| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
| Date: | 2008-04-16 22:22:31 |
| Message-ID: | 20080416152231.1b99c0d8@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Wed, 16 Apr 2008 22:17:30 -0000
"Greg Sabino Mullane" <greg(at)turnstep(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-04-16 22:32:07 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
| Previous Message | Martijn van Oosterhout | 2008-04-16 22:20:01 | Re: Timely reporting of COPY errors |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-04-16 22:32:07 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
| Previous Message | Greg Sabino Mullane | 2008-04-16 22:17:30 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |