Re: deadlock_timeout at < PGC_SIGHUP? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: deadlock_timeout at < PGC_SIGHUP?
Date
Msg-id BANLkTinBZijMDrxJNmDmZPOs4ZJKeenUqw@mail.gmail.com
Whole thread Raw
In response to Re: deadlock_timeout at < PGC_SIGHUP?  (Shigeru Hanada <shigeru.hanada@gmail.com>)
List pgsql-hackers
2011/6/17 Shigeru Hanada <shigeru.hanada@gmail.com>:
> (2011/06/12 6:43), Noah Misch wrote:
>> On Wed, Mar 30, 2011 at 04:48:26PM -0400, Robert Haas wrote:
>>> Me neither.  If making the deadlock timeout PGC_SUSET is independently
>>> useful, I don't object to doing that first, and then we can wait and
>>> see if anyone feels motivated to do more.
>>
>> Here's the patch for that.  Not much to it.
>
> I've reviewed the patch following the article in the PostgreSQL wiki.
> It seems fine except that it needs to be rebased, so I'll mark this
> "Ready for committers'.

OK, committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: pg_upgrade using appname to lock out other users
Next
From: Brendan Jurd
Date:
Subject: Re: Fwd: Keywords in pg_hba.conf should be field-specific