> On Mon, Jul 14, 2008 at 1:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > "Scott Marlowe" <scott.marlowe@gmail.com> writes:
> >> I just got hoisted by my own petard when a pg_dump failed due to
> >> statement timeout and I didn't notice because I was running the dump
> >> nohup and didn't read the nohup.out file to see the errors. It wasn't
> >> a big deal, the data wasn't critical operational data or anything.
> >
> >> But it got me to thinking that maybe pg_dump should disable
> >> statement_timeout when it runs.
> >
> > You mean like this?
> >
> > http://archives.postgresql.org/pgsql-committers/2008-05/msg00026.php
>
> Very cool. I assume it's not in 8.3.3 then?
No, because this is a functionality change, rather than a clear bug.
--
Bruce Momjian <bruce@momjian.us>
EnterpriseDB
+ If your life is a hard drive, Christ can be your backup. +
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
No comments:
Post a Comment