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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
