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

Re: pg_stop_backup does not complete

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stop_backup does not complete
Date: 2010-02-23 20:09:06
Message-ID: 1266955746.1766.106.camel@jd-desktop.unknown.charter.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, 2010-02-23 at 14:49 -0500, Robert Haas wrote:

> > If I issue a shutdown, PostgreSQL should do whatever it needs to do to
> > shutdown; including issuing a pg_stop_backup.
> 
> Maybe.  But for sure, if it doesn't, and instead tells the user to
> issue pg_stop_backup(), then pg_stop_backup() had better WORK when the
> user tries to execute it.

Right.

>   I gather that the problem is that it has to
> finish all that outstanding archiving before shutting down, in which
> case Kevin's suggestion of having a command to abort the backup seems
> reasonable.  I might call it pg_abort_backup() rather than
> pg_fail_backup(), but...
> 

But...?

Joshua D. Drake


> ...Robert
> 


-- 
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.


In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-02-23 20:14:58
Subject: Re: pg_stop_backup does not complete
Previous:From: Kevin GrittnerDate: 2010-02-23 20:01:47
Subject: Re: function side effects

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