Re: Duplicate key issue in a transaction block - Mailing list pgsql-general

From Vyacheslav Kalinin
Subject Re: Duplicate key issue in a transaction block
Date
Msg-id 9b1af80e0906081004w19d463a0q9232f0be898f7947@mail.gmail.com
Whole thread Raw
In response to Re: Duplicate key issue in a transaction block  (Bill Moran <wmoran@potentialtech.com>)
Responses Re: Duplicate key issue in a transaction block
List pgsql-general


On Mon, Jun 8, 2009 at 8:33 PM, Bill Moran <wmoran@potentialtech.com> wrote:

Perhaps you want to take an exclusive lock on the table?  The operation
you describe seems to suggest that you'd want to guarantee exclusive
write access to the table.

Exclusive table lock is a bit excessive  IMO. Locking particular group should be good, though it is not quite straightforward to achieve. I'd use advisory locks or would lock a row in a parent group table (if such table exists, if not - it might be worth to make one) referenced by rows in question.

pgsql-general by date:

Previous
From: Bill Moran
Date:
Subject: Re: Duplicate key issue in a transaction block
Next
From: Madison Kelly
Date:
Subject: Adding the host name to the PgSQL shell