| From: | François Beausoleil <francois(at)teksol(dot)info> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Forums postgresql <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_stop_backup running for 2h10m? |
| Date: | 2013-04-23 20:36:51 |
| Message-ID: | 8ABA25C2-D0E6-4030-BEA6-20DF7F6C27DE@teksol.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le 2013-04-23 à 16:25, Kevin Grittner a écrit :
> François Beausoleil <francois(at)teksol(dot)info> wrote:
>
>> xlogs aren't being added to the backup directory.
>
> Any clue in the server log why that is?
I checked but didn't mention it. I ended up calling pg_cancel_backend() on the process, after 3h. strace on the process revealed pg_stop_backup was doing stat('pg_xlog/archive_status/000###.ready'), but the file never appeared.
As I said, I had written a bad omnipitr command, and was trying to backup to a non-existent host, which would have failed.
I'm recovered now and the backup's going.
Bye,
François
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2013-04-23 21:49:11 | Re: Log messages regarding automatic vacuum and exclusive locks |
| Previous Message | Kevin Grittner | 2013-04-23 20:25:56 | Re: pg_stop_backup running for 2h10m? |