Re: Poor performance of delete by primary key

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Brian Choate <brianc(at)nimblefish(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Poor performance of delete by primary key
Date: 2005-09-07 03:07:04
Message-ID: 431E5958.8040102@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> 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...

Chris

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Christian.Kastner 2005-09-07 09:04:43 Re: Postgresql Hardware - Recommendations
Previous Message Tom Lane 2005-09-07 01:07:27 Re: poor VACUUM performance on large tables