Re: Deadlocks caused by referential integrity checks

From: Vivek Khera <khera(at)kcilink(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Deadlocks caused by referential integrity checks
Date: 2004-08-30 13:58:05
Message-ID: 9D60126E-FA8C-11D8-B1EB-000A9578CFCC@kcilink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Aug 27, 2004, at 5:16 PM, Joshua D. Drake wrote:

>
>> If PG had a way for me to tell it the action logger transaction was
>> "less important" and should be the one killed, I'd live with that,
>> since the other transaction is usually more expensive.
>
> Hello set the check deferrable.

Thanks... On which transaction would I set that? The short one or the
long one? Or both?

And how do you specify that a FK check is deferrable? Do I need to
drop and recreate the FK with the deferrable attribute?

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthew T. O'Connor 2004-08-30 14:10:16 Re: pg_autovacuum start-script
Previous Message Michael Glaesemann 2004-08-30 13:29:56 Re: is last modified timestamp for tables recorded in any system table(s)?