| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: deadlock_timeout |
| Date: | 2008-07-07 15:35:21 |
| Message-ID: | 1215444921.4051.607.camel@ebony.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2008-07-07 at 11:16 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > Why is deadlock_timeout set at SIGHUP?
>
> Because it's not clear what the behavior would be like if different
> backends had different settings ... except that it'd probably be
> surprising.
Yeh, agreed. I was thinking to set the deadlock_timeout the same for all
people running the deadlock-prone transactions and set it higher for
others.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2008-07-07 15:39:57 | Re: Proposal of SE-PostgreSQL patches [try#2] |
| Previous Message | Bernd Helmle | 2008-07-07 15:21:05 | Re: Schema-qualified statements in pg_dump output |