Re: [HACKERS] Proposal: pg_rewind to skip config files
| От | Chris Travers |
|---|---|
| Тема | Re: [HACKERS] Proposal: pg_rewind to skip config files |
| Дата | |
| Msg-id | CAN-RpxCxNBXy8p10XWm-hWOBE6dHRuaZ721oMvt1Khx=7sBcxw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Proposal: pg_rewind to skip config files (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: [HACKERS] Proposal: pg_rewind to skip config files
|
| Список | pgsql-hackers |
On Mon, Sep 4, 2017 at 12:23 PM, Michael Paquier <michael.paquier@gmail.com> wrote:
On Mon, Sep 4, 2017 at 7:21 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> A simple idea would be to pass as a parameter a regex on which we
> check files to skip when scanning the directory of the target remotely
> or locally. This needs to be used with care though, it would be easy
> to corrupt an instance.
I actually shortcut that with a strategy similar to base backups: logs
are on another partition, log_directory uses an absolute path, and
PGDATA has no reference to the log path.
Yeah, it is quite possible to move all these out of the data directory, but bad things can happen when you accidentally copy configuration or logs over those on the target and expecting that all environments will be properly set up to avoid these problems is not always a sane assumption.
So consequently, I think it would be good to fix in the tool. The fundamental question is if there is any reason someone would actually want to copy config files over.
--
Michael
Best Regards,
Chris Travers
Database Administrator
Saarbrücker Straße 37a, 10405 Berlin
В списке pgsql-hackers по дате отправления: