Skip site navigation (1) Skip section navigation (2)

Re: R: Help lock record

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: bitrunner <bitrunner(at)katamail(dot)com>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: R: Help lock record
Date: 2006-05-24 11:31:35
Message-ID: 5F5C13EA-2C78-49F3-83B3-AAF5393B0DFD@fastcrypt.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
On 24-May-06, at 1:12 AM, bitrunner wrote:

>
> On 23-May-06, at 1:37 PM, bitrunner wrote:
>
> > For lock the record I use:
> > select * from orders where id = 17 for update
> >
> > in this way lock the record with id = 17.
> > If an other user demands the same record as I can understand that  
> it is lock?
>
> > yes as long as autocommit is false this is true. In other words as
> > long as you do this inside a transaction/
>
>
> sorry but I dont have to understand.
> How I can understand that there is an other user who lock the record?

I think I understand the question. You want to know how to determine  
if the record is locked.

As far as I know there isn't a way. If process A locks the record,  
then process B attempts to lock the record it will block until  
process A releases the record.

If you have statement_timeout set to some value other than -1 then  
process B will timeout after waiting for the statement_timeout.  
Otherwise it will block until process A is finished with the record.

Dave
>
> Thanks.
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
>               http://www.postgresql.org/docs/faq
>


In response to

pgsql-jdbc by date

Next:From: bitrunnerDate: 2006-05-24 12:28:35
Subject: re_ help lock record
Previous:From: bitrunnerDate: 2006-05-24 05:12:21
Subject: R: Help lock record

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group