Brian Weaver <cmdrclueless(at)gmail(dot)com> writes:
> Doh! I missed a script that was run by cron that does a nightly
> backup. That's the likely offender for the 'copy-to-stdout'
> I've removed it from the nightly run. I'll see if have any better luck
> with this run. Still not sure about the best way to debug the issue
> though. Any pointers would be appreciated.
Well, given that this takes so long, adding PID and time of day to your
log_line_prefix would probably be a smart idea. But at this point it
sounds like what failed was the cron job. Are you sure that the
pg_restore didn't finish just fine? If it didn't, what's the evidence?
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Peter Geoghegan||Date: 2012-05-01 17:56:13|
|Subject: Re: proposal: additional error fields|
|Previous:||From: Brian Weaver||Date: 2012-05-01 17:37:18|
|Subject: Re: Problem with multi-job pg_restore|