Thomas Guettler <[email protected]> writes:
> why does the statement take so long? The column 'lieferant' is indexed. But
> a sequential scan gets done.
It might have something to do with the fact that the planner's idea of
the size of the table is off by a factor of more than 100:
> -> Seq Scan on foo_abc_abc (cost=0.00..468944.11 rows=15404611
> width=8) (actual time=0.029..125458.870 rows=115830 loops=1)
You might need to review your vacuuming policy.
(However, a full table indexscan isn't going to be particularly fast in
any case; it's often the case that seqscan-and-sort is the right
decision. I'm not sure this choice was wrong.)
regards, tom lane
--
Sent via pgsql-general mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
