"Kevin Grittner" writes:
> Brian Weaver wrote:
>> 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 Weaver wrote:
> 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.
It's probably dumping all that
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 wrot
Brian Weaver 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
> tho
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 appre
Here's the steps I'm taking
# pg_restore -l database.dump > database.list
Edit the database.list file and comment out the 'PROCEDURAL LANGUAGE -
plpgsql' item. Because the dump comes from an 8.4 system without
PL/PgSQL installed by default the create language emitted during
pg_restore causes the
Brian Weaver writes:
> I think I've discovered an issue with multi-job pg_restore on a 700 GB
> data file created with pg_dump.
Just to clarify, you mean parallel restore, right? Are you using any
options beyond -j, that is any sort of selective restore?
> The problem occurs during the restore
I think I've discovered an issue with multi-job pg_restore on a 700 GB
data file created with pg_dump. Before anyone points out that the
preferred procedure is to use the newest pg_dump to backup a database
before doing pg_restore let just say, "Yes I'm aware of that advice
and unfortunately it jus
