Re: Duplicate key issue in a transaction block

From: Vyacheslav Kalinin <vka(at)mgcp(dot)com>
To: Bill Moran <wmoran(at)potentialtech(dot)com>
Cc: Ioana Danes <ioanasoftware(at)yahoo(dot)ca>, PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Duplicate key issue in a transaction block
Date: 2009-06-08 17:04:22
Message-ID: 9b1af80e0906081004w19d463a0q9232f0be898f7947@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 8, 2009 at 8:33 PM, Bill Moran <wmoran(at)potentialtech(dot)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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ioana Danes 2009-06-08 17:12:42 Re: Duplicate key issue in a transaction block
Previous Message Madison Kelly 2009-06-08 16:44:51 Adding the host name to the PgSQL shell