Svetlin Manavski <svetlin.manavski@xxxxxxxxx> writes: > The question is: why do we get a seq scan on appqosdata.tcpsessiondata_1 and > appqosdata.tcpsessiondata_2 even if the planner estimates correctly 1 row > out of millions could potentially be selected? As you can see ~90% of the > time is spent on those 2 partitions even if they are not apparently > different from any of the others. Well, there must be *something* different about them. Are you sure they've got the same indexes as the others? It would be useful to see psql's \d report for those partitions, as well as for one of the partitions that's behaving as expected. You might also compare the EXPLAIN results for doing the query on just one child table between the normal and misbehaving partitions. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
