choosing the right locking mode - Mailing list pgsql-general

From rihad
Subject choosing the right locking mode
Date
Msg-id 47F50987.1010603@mail.ru
Whole thread Raw
Responses Re: choosing the right locking mode  ("Scott Marlowe" <scott.marlowe@gmail.com>)
Re: choosing the right locking mode  (Craig Ringer <craig@postnewspapers.com.au>)
Re: choosing the right locking mode  (Sam Mason <sam@samason.me.uk>)
List pgsql-general
Given this type query:

         UPDATE bw_pool
         SET user_id=?
         WHERE bw_id=
                 (SELECT MIN(bw_id) FROM bw_pool WHERE user_id IS NULL)
         RETURNING bw_id

The idea is to "single-threadedly" get at the next available empty slot,
no matter how many such queries run in parallel. So far I've been
semi-successfully using LOCK TABLE bw_pool before the UPDATE, but it
deadlocks sometimes. Maybe I could use some less restrictive locking
mode and prevent possible collisions at the same time?

Thanks.

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong
Next
From: "William Temperley"
Date:
Subject: Secure "where in(a,b,c)" clause.