Re: lock_timeout GUC patch - Mailing list pgsql-hackers

From Tom Lane
Subject Re: lock_timeout GUC patch
Date
Msg-id 8675.1264090110@sss.pgh.pa.us
Whole thread Raw
In response to Re: lock_timeout GUC patch  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jan 21, 2010 at 10:59 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

> What I can see happening is someone setting this GUC in
> postgresql.conf and then being surprised that it applied to thinks
> like walreceiver and autovacuum, in addition to user queries.  Are we
> even sure that that code would all behave sanely with this behavior?

No, I'm not sure, as I said before ;-).  But a 100%-arbitrary
restriction like "it doesn't apply to background processes" will not
make it noticeably safer.  There is very damn little code that only
executes in background and never anywhere else.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: About "Our CLUSTER implementation is pessimal" patch
Next
From: Boszormenyi Zoltan
Date:
Subject: Re: lock_timeout GUC patch