Thread: deadlock_timeout

Why is deadlock_timeout set at SIGHUP?

If it effects statement behaviour it ought to be a USERSET. Using CPU
time isn't a problem we protect against anywhere else.

I'd like to be able to set deadlock-prone transactions lower, yet keep a
fairly high setting for others.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support

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.
        regards, tom lane

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

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.

I have added a code comment explaining this.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +