Skip site navigation (1) Skip section navigation (2)

Re: pg_stop_backup does not complete

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, 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:56:14
Message-ID: C32B5D9B-A768-4AE2-B69C-4E2ABF3B8F3D@kineticode.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Feb 24, 2010, at 12:47 PM, Tom Lane wrote:

>> 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.
> 
> The pg_abort_backup() operation previously proposed seems like the only
> workable compromise.  Simon is quite right to not want pg_stop_backup()
> to behave in a way that could contribute to data loss; but on the other
> hand there needs to be some clear way to get the system out of that
> state at need.

+1 makes sense.

David


In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-02-24 21:01:02
Subject: Re: pg_stop_backup does not complete
Previous:From: Tom LaneDate: 2010-02-24 20:47:02
Subject: Re: pg_stop_backup does not complete

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group