Re: BUG #1633: about transactions and row level locking

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: deepak <deepak(at)jtech(dot)co(dot)in>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-general(at)postgresql(dot)org
Subject: Re: BUG #1633: about transactions and row level locking
Date: 2005-04-28 01:32:28
Message-ID: 20050428013228.GA19750@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-general

On Wed, Apr 27, 2005 at 13:56:02 +0100,
deepak <deepak(at)jtech(dot)co(dot)in> wrote:
>
> The following bug has been logged online:

This isn't a bug, its a question. I am moving the discussion over to
the general list.

> Bug reference: 1633
> Logged by: deepak
> Email address: deepak(at)jtech(dot)co(dot)in
> PostgreSQL version: 8.0.1
> Operating system: MS windows 2000 Server
> Description: about transactions and row level locking
> Details:
>
> How we can know a record is locked before updating the record. The purpose
> is to avoid deadlock or queuing of update statements while using "select *
> from table for update".

You might be able to use a short timeout on the statement that tries the
update.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Fredrik Olsson 2005-04-28 15:31:45 BUG #1636: Foreign key referencing inherited table fails.
Previous Message Oliver Jowett 2005-04-27 23:35:30 Re: BUG #1628: JDBC bug with regard to text column data type

Browse pgsql-general by date

  From Date Subject
Next Message Bruno Wolff III 2005-04-28 01:44:36 Re: Reduce size of $PGDATA for "demo cdrom"?
Previous Message Tom Lane 2005-04-28 01:22:42 Re: I must be daft, but I can't figure out what is wrong with this