| From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
|---|---|
| To: | "Cray2" <cray2(at)mail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Row Level Locking Problem |
| Date: | 2000-08-21 00:31:03 |
| Message-ID: | 3.0.1.32.20000820173103.014d2d60@mail.pacifier.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Warner | 2000-08-21 01:44:49 | Re: Bug tracking (was Re: +/- Inf for float8's) |
| Previous Message | Don Baccus | 2000-08-20 23:49:57 | Re: Optimisation deficiency: currval('seq')-->seq scan, constant-->index scan |