Postgres Pro
Downloads
Home   >   mailing lists

Re: deadlock_timeout - Mailing list pgsql-hackers

From Tom Lane
Subject Re: deadlock_timeout
Date
Msg-id 10462.1215443784@sss.pgh.pa.us
Whole thread Raw
In response to deadlock_timeout  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: deadlock_timeout  (Simon Riggs <simon@2ndquadrant.com>)
Re: deadlock_timeout  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Schema-qualified statements in pg_dump output
Next
From: Bernd Helmle
Date:
Subject: Re: Schema-qualified statements in pg_dump output