Re: lock_timeout GUC patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: lock_timeout GUC patch
Date
Msg-id 8492.1264089561@sss.pgh.pa.us
Whole thread Raw
In response to Re: lock_timeout GUC patch  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: lock_timeout GUC patch  (Robert Haas <robertmhaas@gmail.com>)
Re: lock_timeout GUC patch  (Boszormenyi Zoltan <zb@cybertec.at>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jan 21, 2010 at 9:41 AM, Boszormenyi Zoltan <zb@cybertec.at> wrote:
>> I would like a mini-review on the change I made in the latest
>> patch by introducing the validator function. Is it enough
>> to check for
>> � �(source == PGC_S_DEFAULT || source == PGC_S_SESSION)
>> to ensure only interactive sessions can get lock timeouts?

> I'm not sure that I know how this should work, but that approach seems
> a little strange to me.  Why would we not allow PGC_S_USER, for
> example?

Why is this a good idea at all?  I can easily see somebody feeling that
he'd like autovacuums to fail rather than block on locks for a long
time, for example.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Leonardo F
Date:
Subject: Re: About "Our CLUSTER implementation is pessimal" patch
Next
From: Robert Haas
Date:
Subject: Re: lock_timeout GUC patch