Re: pg_stop_backup does not complete

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Josh Berkus" <josh(at)agliodbs(dot)com>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(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:40:17
Message-ID: 4B853A51020000250002F60F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> 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.

So maybe pg_abort_backup() is needed for 9.0 after all?

(1) You'd want to be able to run it either instead of
pg_stop_backup or to interrupt a pending one.

(2) You wouldn't want the .backup file to be written.

(3) What about the equivalent WAL end-of-backup record?

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2010-02-24 20:46:59 Re: pg_stop_backup does not complete
Previous Message Heikki Linnakangas 2010-02-24 20:39:45 Re: pg_stop_backup does not complete