Re: Need some help in postgres locking mechanism

From: santhosh kumar <kurasanthoshkumar(at)gmail(dot)com>
To: Hannes Erven <hannes(at)erven(dot)at>
Cc: Vick Khera <vivek(at)khera(dot)org>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Need some help in postgres locking mechanism
Date: 2014-04-08 16:12:23
Message-ID: CAOE+M7EGxMOjDAL6v2MmdjtfHFrcoAJopQX6Jpe3cDh5z2xT+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks alot..i have implemented in same format.You people are awesome.Thank
You once again

On Tue, Apr 8, 2014 at 8:58 PM, Hannes Erven <hannes(at)erven(dot)at> wrote:

> Hi,
>
>
> 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
>
>
>
> -hannes
>

--
K.Santhosh Kumar
Member of Technical Staff
Groupon,Chennai

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vick Khera 2014-04-08 17:41:44 Re: Need some help in postgres locking mechanism
Previous Message Hannes Erven 2014-04-08 15:28:48 Re: Need some help in postgres locking mechanism