Re: Problem with multi-job pg_restore
| От | Tom Lane |
|---|---|
| Тема | Re: Problem with multi-job pg_restore |
| Дата | |
| Msg-id | 18112.1335897778@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Problem with multi-job pg_restore ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
| Список | pgsql-hackers |
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> Brian Weaver <cmdrclueless@gmail.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
В списке pgsql-hackers по дате отправления: