| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: deadlock_timeout at < PGC_SIGHUP? |
| Date: | 2011-06-22 02:37:31 |
| Message-ID: | BANLkTinBZijMDrxJNmDmZPOs4ZJKeenUqw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2011/6/17 Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2011-06-22 02:38:36 | Re: Fwd: Keywords in pg_hba.conf should be field-specific |
| Previous Message | Bruce Momjian | 2011-06-22 02:33:43 | Re: pg_upgrade using appname to lock out other users |