deadlock_timeout

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: deadlock_timeout
Date: 2008-07-07 15:11:33
Message-ID: 1215443493.4051.600.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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.com
PostgreSQL Training, Services and Support

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-07-07 15:13:13 Userset logging
Previous Message Andrew Dunstan 2008-07-07 15:09:56 Re: Schema-qualified statements in pg_dump output