Tom, The restore appears to have finished without a problem. The issue I have is a running instance of postgres is still active in a COPY state after the restore. The process is running full tilt, almost like it's in a tight loop condition.
-- Brian On Tue, May 1, 2012 at 1:44 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Brian Weaver <cmdrcluel...@gmail.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 -- /* insert witty comment here */ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
