Re: [COMMITTERS] pgsql: Allow external recovery_config_directory - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [COMMITTERS] pgsql: Allow external recovery_config_directory
Date
Msg-id CA+U5nMLx_CFfqd5tTKfnbwW_-GgsNancpNwsvJxnn0g8eu3baA@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Allow external recovery_config_directory  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
On 28 March 2013 13:47, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:

>> Therefore anybody using pg_basebackup and the config_file parameter
>> does *not* have an executable backup when used with the -R option, as
>> Heikki was suggesting was a requirement for this patch.
>
>
> That's not related to the -R option, the situation with config_file is the
> same with or without it.

Yes, it is related to -R. You said that with -R we are expecting to
have a fully executable backup, which won't happen because the config
files are missing.

That is the situation now and the fact the patch had the same issue is
not relevant. It's a pre-existing issue.

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Catching resource leaks during WAL replay
Next
From: Tom Lane
Date:
Subject: Re: Catching resource leaks during WAL replay