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

From Joshua D. Drake
Subject Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout
Date
Msg-id 20080416152231.1b99c0d8@commandprompt.com
Whole thread Raw
In response to Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout  ("Greg Sabino Mullane" <greg@turnstep.com>)
Responses Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Wed, 16 Apr 2008 22:17:30 -0000
"Greg Sabino Mullane" <greg@turnstep.com> wrote:
> I don't think it's fair to simply discard the use cases provided as
> "implausible" and demand one more to your liking. I strongly dislike
> having a giant dump file written that has non-vital configuration
> variables embedded in the top of it, precluding any user choice
> whatsoever[1]. As before, where are the reports of all the people
> having their manual restorations interrupted by a statement_timeout?

Calling me, wondering why in the world it is happening.

Joshua D. Drake

-- 
The PostgreSQL Company since 1997: http://www.commandprompt.com/ 
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate




pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Timely reporting of COPY errors
Next
From: Chris Browne
Date:
Subject: Re: Lessons from commit fest