Re: Row Level Locking Problem - Mailing list pgsql-hackers

From Don Baccus
Subject Re: Row Level Locking Problem
Date
Msg-id 3.0.1.32.20000820173103.014d2d60@mail.pacifier.com
Whole thread Raw
In response to Row Level Locking Problem  ("Cray2" <cray2@mail.com>)
List pgsql-hackers
At 02:33 PM 8/20/00 +0200, Cray2 wrote:
>    I have a big problem, when I try to lock a row locked previouly, It wait
>until commit / rollback operation.
>
>        How could lock a row if It is not locked already?
>
>        Could I now if a row is locked?
>
>        Could I get some error message from postgres when I do 'select ....
>for update' to a locked row instead of wait for commit / rollback?

Well, this is how it is supposed to work.  "select for update" only
works within a transaction and holds the lock until the transaction
is complete.

What exactly is it that you're trying to do?



- Don Baccus, Portland OR <dhogaza@pacifier.com> Nature photos, on-line guides, Pacific Northwest Rare Bird Alert
Serviceand other goodies at http://donb.photo.net.
 


pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Optimisation deficiency: currval('seq')-->seqscan, constant-->index scan
Next
From: Philip Warner
Date:
Subject: Re: Bug tracking (was Re: +/- Inf for float8's)