From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_stop_backup does not complete |
Date: | 2010-02-24 20:39:45 |
Message-ID: | 4B858E91.702@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Josh Berkus wrote:
>> pg_stop_backup() doesn't complete until all the WAL segments needed to
>> restore from the backup are archived. If archive_command is failing,
>> that never happens.
>
> OK, so we need a way out of that cycle if the user is issuing
> pg_stop_backup because they *already know* that archive_command is
> failing. Right now, there's no way out other than a fast shutdown,
Sure there is. Just kill the session, Ctrl-c or similar.
pg_stop_backup() isn't actually doing anything at that point anymore;
it's just waiting for the files to be archived before returning.
Or fix archive_command, and pg_reload_conf().
BTW, if you want a timeout for that, you can use statement_timeout.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-02-24 20:40:17 | Re: pg_stop_backup does not complete |
Previous Message | Joshua D. Drake | 2010-02-24 20:37:07 | Re: pg_stop_backup does not complete |