Larry Rosenman <l...@lerctr.org> writes:
> On 2013-05-09 16:22, Tom Lane wrote:
>> Perhaps it's blocked on a lock? Did you look into pg_locks?
>> Did you note whether the process was consuming CPU time and/or doing
>> IO?
> all the locks were clear, and it was consuming CPU and doing I/O
> (D->S->D state), etc.
Hm. I'm suspicious that you still ended up with a seqscan checking
plan. Was this session started after you added all the missing indexes?
If not, it seems possible that it was using a bad pre-cached plan.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
