Re: Problem with multi-job pg_restore - Mailing list pgsql-hackers

From Brian Weaver
Subject Re: Problem with multi-job pg_restore
Date
Msg-id CAAhXZGtCTRwqmzRSf24v8UHfVOpbCYVUrP4V-ufdoUFFqFXv7g@mail.gmail.com
Whole thread Raw
In response to Re: Problem with multi-job pg_restore  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Problem with multi-job pg_restore
List pgsql-hackers
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@sss.pgh.pa.us> wrote:
> Brian Weaver <cmdrclueless@gmail.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 */


pgsql-hackers by date:

Previous
From: Brian Weaver
Date:
Subject: Re: Problem with multi-job pg_restore
Next
From: Tom Lane
Date:
Subject: Re: Problem with multi-job pg_restore