| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Hans-Juergen Schoenig <postgres(at)cybertec(dot)at> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SELECT ... FOR UPDATE [WAIT integer | NOWAIT] for 8.5 |
| Date: | 2009-06-02 16:41:00 |
| Message-ID: | 200906021641.n52Gf0E14636@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-02 16:41:21 | Re: pg_standby -l might destory the archived file |
| Previous Message | Tom Lane | 2009-06-02 16:33:51 | Re: Managing multiple branches in git |