| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Pgsql General list" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: statement timeout and pg_dump |
| Date: | 2008-07-14 19:17:39 |
| Message-ID: | dcc563d10807141217u7466d20bva7cf734bdc7ea2d0@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Hoy | 2008-07-14 19:54:31 | optimizer ignoring primary key and doing sequence scan |
| Previous Message | Tom Lane | 2008-07-14 19:02:04 | Re: statement timeout and pg_dump |