| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] 'Waiting on lock' |
| Date: | 2007-06-19 22:29:22 |
| Message-ID: | 20070619222922.GS7531@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
* Simon Riggs (simon(at)2ndquadrant(dot)com) wrote:
> related TODO items:
> - add a WAIT n clause in same SQL locations as NOWAIT
> - add a lock_wait_timeout (USERSET), default = 0 (unlimited waiting)
>
> to provide better control over lock waits.
I havn't had a chance to look over the commit yet, sorry, but it sounds
like it's only logging to the log file? Was hoping to get a NOTICE back
out to the user for at least the 'still waiting on lock x' log, after
the deadlock detection. I'm not particular about gucs/settings/etc,
whatever people feel is best, provided there's a way to get the messages
in psql. :)
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-06-19 22:57:19 | Re: [HACKERS] 'Waiting on lock' |
| Previous Message | Simon Riggs | 2007-06-19 21:34:52 | Re: [HACKERS] 'Waiting on lock' |