From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Massalin Yerzhan <yerzhik(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Simple delete query is taking too long (never ends) |
Date: | 2015-11-12 15:12:51 |
Message-ID: | CAHyXU0wNYJQwW+m0vP_GaSmY6yh82WxB8+425TziJPVMAu-dVA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Nov 11, 2015 at 1:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Massalin Yerzhan <yerzhik(at)gmail(dot)com> writes:
>> I'm having an issue. The query never ends:
>> delete from bb_gamelist_league;
>
> 9 times out of 10, the answer to this type of problem is that you have
> some table referencing this one by a foreign key, and the referencing
> column is not indexed. PG doesn't require such an index, but lack of
> one will mean that retail checks or deletions of referencing rows are
> really slow.
>
> If you're not sure which table is the problem, try doing an EXPLAIN
> ANALYZE of a DELETE that will only remove a few rows. You should
> see some time blamed on a trigger associated with the FK constraint.
You've answered this question (with the same answer) what feels like a
gazillion times. I guess the underlying problem is that EXPLAIN is,
uh, not explaining things very well.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-11-12 15:36:35 | Re: Simple delete query is taking too long (never ends) |
Previous Message | Tom Lane | 2015-11-11 19:33:35 | Re: Simple delete query is taking too long (never ends) |