| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jonatan Evald Buus <jonatan(dot)buus(at)cellpointmobile(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Poor performance for delete query |
| Date: | 2014-04-25 14:36:44 |
| Message-ID: | 6664.1398436604@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Jonatan Evald Buus <jonatan(dot)buus(at)cellpointmobile(dot)com> writes:
> On 24 April 2014 23:25, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Jonatan Evald Buus <jonatan(dot)buus(at)cellpointmobile(dot)com> writes:
>>> Why is "order2transaction_fk" being triggered twice? Is that because
>>> there're two affected rows?
>> No, I'd have expected a delete of multiple rows to show as calls=N,
>> not N separate entries.
> This doesn't explain the extra trigger of "order2transaction_fk".
> Any guidelines as to how we may investigate this further would be greatly
> appreciated.
If you could show us your exact database schema, it might become
clearer what's happening. I'm wondering about duplicate constraint names
for instance ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Elanchezhiyan Elango | 2014-04-27 12:08:07 | Checkpoints and slow queries |
| Previous Message | Дмитрий Шалашов | 2014-04-25 10:36:18 | Re: Server vacuuming the same table again and again |