From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Larry Rosenman <ler(at)lerctr(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: LONG delete with LOTS of FK's |
Date: | 2013-05-09 21:40:49 |
Message-ID: | 7092.1368135649@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Larry Rosenman <ler(at)lerctr(dot)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(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
From | Date | Subject | |
---|---|---|---|
Next Message | Evan D. Hoffman | 2013-05-09 21:41:39 | Re: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4 |
Previous Message | Bruce Momjian | 2013-05-09 21:29:02 | Re: Re: [GENERAL] pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4 |