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
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>
Comments: In-reply-to Jonatan Evald Buus <jonatan.buus@cellpointmobile.com>
 message dated "Fri, 25 Apr 2014 07:04:59 +0200"
Date: Fri, 25 Apr 2014 10:36:44 -0400
Message-ID: <6664.1398436604@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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