Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Date
Msg-id 200804171518.55929.peter_e@gmx.net
Whole thread Raw
In response to Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout  (Heikki Linnakangas <heikki@enterprisedb.com>)
Responses Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
Heikki Linnakangas wrote:
> Sorry if I missed it in the original thread, but what is the use case
> you have in mind?

I think the bottom line is just that having statement_timeout a global setting 
is stupid for a variety of reasons (dump, restore, vacuum, locks, incidental 
delays) that we should discourage it (or prevent it, as proposed elsewhere) 
rather than working around it in countless individual places.


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Repair two places whereSIGTERM exit couldleave shared memory
Next
From: Magnus Hagander
Date:
Subject: Re: get rid of psql welcome message