Re: [pg_rewind] cp: cannot stat ‘pg_wal/RECOVERYHISTORY’: No such file or directory

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: [pg_rewind] cp: cannot stat ‘pg_wal/RECOVERYHISTORY’: No such file or directory
Date: 2019-06-10 13:49:19
Message-ID: CA+TgmoaXua9Av=S9pe_VNXjrsMfoyhHLB9wfJaSPYe2Lp5Agxw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 10, 2019 at 7:08 AM Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com> wrote:
> This can surely be fixed from the script. While configuring the old
> master as a standby server, clear/modify the settings in
> postgresql.auto.conf. But, it contradicts with the comment in the file
> which forbids the user from editing the file.

The user isn't really forbidden from editing the file. They can do so
safely when the server is down.

This whole thing looks like a nonissue to me. If you set it up wrong,
it won't work. So don't do that.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-06-10 14:19:27 Re: postgres_fdw: unordered C includes
Previous Message Alvaro Herrera 2019-06-10 13:44:08 Re: Should we warn against using too many partitions?