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

Re: Cluster feature: Start/stop archiving at runtime

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-cluster-hackers(at)postgresql(dot)org
Subject: Re: Cluster feature: Start/stop archiving at runtime
Date: 2010-03-02 07:30:50
Message-ID: 3f0b79eb1003012330s545e13ffk41c4332aeeccfb8@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-cluster-hackers
On Sun, Feb 28, 2010 at 9:08 PM, Martin Pihlak <martin(dot)pihlak(at)gmail(dot)com> wrote:
> Greg Smith wrote:
>> Next up is "Start/stop archiving at runtime".  First set of questions:
>>
>> -Is this referring to the current PITR archiving as done via
>> archive_command, does it intend to cover a wider scope than that, or is
>> "archiving" being used in a general replication sense instead not
>> related to that?
>>
>> -What is the issue with Skype and failed nodes this is alluding to?
>>
>
> AFAIK the only issue is that we cannot set archive_mode without restarting
> Postgres. This leads to archive_mode always set to "on" and a dummy
> archive_command being used. The background for this is that we don't know
> in advance when we need to create a PITR clone of a particular database.

Changing archive_command and reloading the postgresql.conf (signaling
a SIGHUP) is not sufficient for you? You only need more user-friendly
API to do that? Or more intelligent functionality?

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

pgsql-cluster-hackers by date

Next:From: Tatsuo IshiiDate: 2010-03-02 07:42:09
Subject: Re: Cluster feature: Start/stop archiving at runtime
Previous:From: Ing . Marcos Luís Ortíz ValmasedaDate: 2010-02-28 18:12:04
Subject: Re: Cluster feature: Start/stop archiving at runtime

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