From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonatan Evald Buus <jonatan.buus@cellpointmobile.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Poor performance for delete query
Date: Fri, 25 Apr 2014 10:36:44 -0400
Message-ID: <6664.1398436604@sss.pgh.pa.us> (raw)
In-Reply-To: <CABnF-8KDPLLDo10VhHEOu=fC-jyLnQzYjVU56RmQWkiDPDaL9g@mail.gmail.com>
References: <CABnF-8Lyps8ribpp=BOFnqGEeWp2K5iuLukMo3txQ5UkgHjF7g@mail.gmail.com>
<28604.1398371340@sss.pgh.pa.us>
<CABnF-8J9G7XfEuyV-DhUb3VkuZ_XCF=t7_okJFW7nZ1qMmi94Q@mail.gmail.com>
<29874.1398374703@sss.pgh.pa.us>
<CABnF-8KDPLLDo10VhHEOu=fC-jyLnQzYjVU56RmQWkiDPDaL9g@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Jonatan Evald Buus <jonatan.buus@cellpointmobile.com> writes:
> On 24 April 2014 23:25, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Jonatan Evald Buus <jonatan.buus@cellpointmobile.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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, jonatan.buus@cellpointmobile.com
Subject: Re: Poor performance for delete query
In-Reply-To: <6664.1398436604@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox