Postgres Pro
Downloads
Home   >   mailing lists

deadlock_timeout - Mailing list pgsql-hackers

From Simon Riggs
Subject deadlock_timeout
Date
Msg-id 1215443493.4051.600.camel@ebony.site
Whole thread Raw
Responses Re: deadlock_timeout  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: PATCH: CITEXT 2.0 v2
Next
From: Tom Lane
Date:
Subject: Re: Schema-qualified statements in pg_dump output