Re: [HACKERS] 'Waiting on lock' - Mailing list pgsql-patches

From Stephen Frost
Subject Re: [HACKERS] 'Waiting on lock'
Date
Msg-id 20070619222922.GS7531@tamriel.snowman.net
Whole thread Raw
In response to Re: [HACKERS] 'Waiting on lock'  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: [HACKERS] 'Waiting on lock'  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
* Simon Riggs (simon@2ndquadrant.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

Attachment

pgsql-patches by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: [HACKERS] 'Waiting on lock'
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] 'Waiting on lock'