Search Postgresql Archives

Re: Duplicate key issue in a transaction block

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In response to Vyacheslav Kalinin <vka@xxxxxxxx>:

> On Mon, Jun 8, 2009 at 8:33 PM, Bill Moran <wmoran@xxxxxxxxxxxxxxxxx> 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.

Perhaps, but sounds like a lot of unnecessary complexity to me.

... and I didn't say exclusive table lock, I said "exclusive write"  Big
difference there.

-- 
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux