| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, 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:37:07 |
| Message-ID: | 1267043827.17525.134.camel@jd-desktop.unknown.charter.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2010-02-24 at 12:32 -0800, 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,
> which is a bit user-hostile.
Hmmm well... changing the archive_command to /bin/true and issuing a HUP
would cause the command to succeed, but I still think that is over the
top. I prefer Kevin's solution or some variant thereof:
http://archives.postgresql.org/pgsql-hackers/2010-02/msg01853.php
http://archives.postgresql.org/pgsql-hackers/2010-02/msg01907.php
Sincerely,
Joshua D. Drake
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-02-24 20:39:45 | Re: pg_stop_backup does not complete |
| Previous Message | Josh Berkus | 2010-02-24 20:32:28 | Re: pg_stop_backup does not complete |