Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5
Date
Msg-id 1253859923.26523.1.camel@fsopti579.F-Secure.com
Whole thread Raw
In response to Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Wed, 2009-09-23 at 10:58 -0700, Josh Berkus wrote:
> So, while some people have asserted that a lock_timeout GUC would
> allow
> users to retrofit older applications to time out on locks, I just
> don't
> see that being the case.  You'd have to refactor regardless, and if
> you're going to, just add the WAIT statement to the lock request.

But note that almost every statement contains a lock request of some
kind.  So you'd need to add a WAIT clause to every single statement type
in PostgreSQL.



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [GENERAL] libpq port number handling
Next
From: Peter Eisentraut
Date:
Subject: Re: [GENERAL] libpq port number handling