Re: Problem with multi-job pg_restore

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Brian Weaver" <cmdrclueless(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem with multi-job pg_restore
Date: 2012-05-01 18:15:08
Message-ID: 4F9FE1DC0200002500047640@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-05-01 18:42:58 Re: Problem with multi-job pg_restore
Previous Message Andrew Dunstan 2012-05-01 18:11:52 Re: JSON in 9.2 - Could we have just one to_json() function instead of two separate versions ?