Scott Marlowe wrote:
> On Mon, Jul 14, 2008 at 1:02 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> > "Scott Marlowe" <[EMAIL PROTECTED]> 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
On Mon, Jul 14, 2008 at 1:02 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Scott Marlowe" <[EMAIL PROTECTED]> 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
"Scott Marlowe" <[EMAIL PROTECTED]> 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 opera
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
