Re: Poor performance of delete by primary key - Mailing list pgsql-performance

From Jim C. Nasby
Subject Re: Poor performance of delete by primary key
Date
Msg-id 20050907213834.GB83885@pervasive.com
Whole thread Raw
In response to Re: Poor performance of delete by primary key  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-performance
On Wed, Sep 07, 2005 at 11:07:04AM +0800, Christopher Kings-Lynne wrote:
> >Unfortunately there's no very simple way to determine which FK is the
> >problem.  (In 8.1 it'll be possible to do that with EXPLAIN ANALYZE,
> >but in existing releases EXPLAIN doesn't break out the time spent in
> >each trigger ...)  You have to just eyeball the schema :-(.
>
> phpPgAdmin has a handy info feature where you can see all tables that
> refer to the current one.  You can always go and steal that query to
> find them...

You can also use pg_user_foreighn_key* from
http://pgfoundry.org/projects/newsysviews/.
--
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Query take 101 minutes, help, please
Next
From: "wisan watcharinporn"
Date:
Subject: please comment on cpu 32 bit or 64 bit