Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5

Alvaro Herrera <alvherre@commandprompt.com>

From: Alvaro Herrera <alvherre@commandprompt.com>
To: Boszormenyi Zoltan <zb@cybertec.at>
Cc: Bruce Momjian <bruce@momjian.us>, Hans-Juergen Schoenig <postgres@cybertec.at>, Josh Berkus <josh@agliodbs.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgresql.org
Date: 2009-07-27T13:00:30Z
Lists: pgsql-hackers
Boszormenyi Zoltan wrote:
> Alvaro Herrera írta:
> > Boszormenyi Zoltan wrote:
> >   
> >> The vague consensus for syntax options was that the GUC
> >> 'lock_timeout' and WAIT [N] extension (wherever NOWAIT
> >> is allowed) both should be implemented.
> >>
> >> Behaviour would be that N seconds timeout should be
> >> applied to every lock that the statement would take.
> >
> > In http://archives.postgresql.org/message-id/291.1242053201@sss.pgh.pa.us
> > Tom argues that lock_timeout should be sufficient.  I'm not sure what
> > does WAIT [N] buy.
> 
> Syntax consistency with NOWAIT?

Consistency could also be achieved by removing NOWAIT, but I don't see
you proposing that.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support