Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>
Subject: Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Date: 2008-04-18 06:34:49
Message-ID: 20080418063449.GA2482@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Thu, Apr 17, 2008 at 03:18:54PM +0200, Peter Eisentraut wrote:
> 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.

maintainence_statement_timeout? :)

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bryce Nesbitt 2008-04-18 06:36:14 Re: Proposed patch - psql wraps at window width
Previous Message Joshua D. Drake 2008-04-18 04:58:48 Re: get rid of psql welcome message

Browse pgsql-patches by date

  From Date Subject
Next Message Bryce Nesbitt 2008-04-18 06:36:14 Re: Proposed patch - psql wraps at window width
Previous Message Tom Lane 2008-04-18 04:31:25 Re: Proposed patch - psql wraps at window width