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.
On Tue, May 1, 2012 at 12:59 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Brian Weaver <cmdrclueless(at)gmail(dot)com> writes:
> I'm confused. A copy-to-stdout ought to be something that pg_dump
> would do, not pg_restore. Are you sure this is related at all?
> regards, tom lane
/* insert witty comment here */
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-05-01 17:44:06|
|Subject: Re: Problem with multi-job pg_restore |
|Previous:||From: Brian Weaver||Date: 2012-05-01 17:30:01|
|Subject: Re: Problem with multi-job pg_restore|