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

Re: pg_stop_backup does not complete

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, jd(at)commandprompt(dot)com, Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stop_backup does not complete
Date: 2010-03-02 13:19:43
Message-ID: 1267535983.21887.3.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, 2010-03-02 at 13:13 +0000, Greg Stark wrote:
> On Tue, Mar 2, 2010 at 9:48 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> >> > Setting archive_mode to a command that does nothing but return true, e.g. /bin/true,
> >>
> >> "return true" seems ambiguous for me. How about writing clearly
> >> "return a zero exit status" instead?
> >
> > Docs are already quite clear on that point. I think we should avoid
> > specifying it twice.
> >
> 
> Why do we disallow turning off archive_mode anyways? 

Because it is needed for safety and nobody has got around to coding the
idea of turning it on/off during normal running, which is possible, with
appropriate care.

> I understand not
> turning it on -- though even that would be nice if it "took effect
> after the next checkpoint" but turning it off should always be safe,
> no?

We don't support that behaviour in parameters.

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

Responses

pgsql-hackers by date

Next:From: Greg SmithDate: 2010-03-02 13:32:53
Subject: Re: pg_stop_backup does not complete
Previous:From: Greg StarkDate: 2010-03-02 13:13:37
Subject: Re: pg_stop_backup does not complete

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