Re: Deadlocks caused by referential integrity checks - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: Deadlocks caused by referential integrity checks
Date
Msg-id 412FA4BE.9070101@commandprompt.com
Whole thread Raw
In response to Re: Deadlocks caused by referential integrity checks  (Vivek Khera <khera@kcilink.com>)
Responses Re: Deadlocks caused by referential integrity checks
List pgsql-general
>
> 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.


>
>


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
Mammoth PostgreSQL Replicator. Integrated Replication for PostgreSQL

Attachment

pgsql-general by date:

Previous
From: Ennio-Sr
Date:
Subject: [OT?] Problems with majordomo :-)
Next
From: "Matthew T. O'Connor"
Date:
Subject: Re: pg_autovacuum start-script