On Sun, Feb 28, 2010 at 9:08 PM, Martin Pihlak <martin.pihlak@gmail.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