Re: Need some help in postgres locking mechanism - Mailing list pgsql-general

From Vick Khera
Subject Re: Need some help in postgres locking mechanism
Date
Msg-id CALd+dceh7be0t0B6xKuyQMLbyUsse1MTz99rG7Sh2mh00j7t+w@mail.gmail.com
Whole thread Raw
In response to Re: Need some help in postgres locking mechanism  (Hannes Erven <hannes@erven.at>)
List pgsql-general
On Tue, Apr 8, 2014 at 11:28 AM, Hannes Erven <hannes@erven.at> wrote:
> On 2014-04-08 15:27, Vick Khera wrote:
> [...]
>>
>> Problem 2: you cannot have a second process skip over locked rows.
>
>
>
> In fact, you can: use "FOR UPDATE NOWAIT" and catch any errors.
>
> e.g. SELECT * FROM jobqueue WHERE id=? FOR UPDATE NOWAIT

That's not really skipping over the locked rows and returning the next
row, that's bailing out and retrying.


pgsql-general by date:

Previous
From: Hannes Erven
Date:
Subject: Re: Need some help in postgres locking mechanism
Next
From: Steve Kehlet
Date:
Subject: is there a way to firmly cap postgres worker memory consumption?