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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers