From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql General list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: statement timeout and pg_dump |
Date: | 2008-07-14 21:16:56 |
Message-ID: | 200807142116.m6ELGuc06770@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Scott Marlowe wrote:
> On Mon, Jul 14, 2008 at 1:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | JD Wong | 2008-07-14 21:37:28 | plperl installation |
Previous Message | Mason Hale | 2008-07-14 21:08:32 | vacuum taking an unusually long time |