Date: Wed, 7 Sep 2005 16:38:34 -0500
From: "Jim C. Nasby" <jnasby@pervasive.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Brian Choate <brianc@nimblefish.com>,
	pgsql-performance@postgresql.org
Subject: Re: Poor performance of delete by primary key
Message-ID: <20050907213834.GB83885@pervasive.com>
References: 
 <2F9239F5E316C54688FDA9814FF045D6EADACC@EXCHANGE.sf.nimblefish.com>
	<18162.1126020720@sss.pgh.pa.us>
	<431E5958.8040102@familyhealth.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <431E5958.8040102@familyhealth.com.au>
User-Agent: Mutt/1.5.9i

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