From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | "Brian Weaver" <cmdrclueless(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Problem with multi-job pg_restore |
Date: | 2012-05-01 18:42:58 |
Message-ID: | 18112.1335897778@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Brian Weaver <cmdrclueless(at)gmail(dot)com> 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 new data you just restored to ...
> somewhere. You'll need to review the crontab job (or maybe ps
> output) to figure out where.
Or even more likely, it's reading all that data and deciding that
it doesn't need to output it because it's not visible to its snapshot;
that could look like a pretty tight loop from outside. If the connected
cron job has gone away, I'd suggest just SIGINT'ing the COPY job.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2012-05-01 19:01:18 | Re: extending relations more efficiently |
Previous Message | Kevin Grittner | 2012-05-01 18:15:08 | Re: Problem with multi-job pg_restore |