On Mon, 2008-07-07 at 11:16 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.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.comPostgreSQL Training, Services and Support
