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

From Bruce Momjian
Subject Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5
Date
Msg-id 200906021641.n52Gf0E14636@momjian.us
Whole thread Raw
In response to Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5  (Hans-Juergen Schoenig <postgres@cybertec.at>)
Responses Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5  (Boszormenyi Zoltan <zb@cybertec.at>)
List pgsql-hackers
Hans-Juergen Schoenig wrote:
> hello everybody,
> 
> from my side the goal of this discussion is to extract a consensus so 
> that we can go ahead and implement this issue for 8.5.
> our customer here needs a solution to this problem and we have to come 
> up with something which can then make it into PostgreSQL core.
> how shall we proceed with the decision finding process here?
> i am fine with a GUC and with an grammar extension - i just need a 
> decision which stays unchanged.

Do we have answer for Hans-Juergen here?

I have added a vague TODO:
       Consider a lock timeout parameter       * http://archives.postgresql.org/pgsql-hackers/2009-05/msg00485.php 

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Managing multiple branches in git
Next
From: Tom Lane
Date:
Subject: Re: pg_standby -l might destory the archived file