Re: Data-only pg_rewind, take 2 - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Data-only pg_rewind, take 2
Date
Msg-id 20190318040942.GD1885@paquier.xyz
Whole thread Raw
In response to Data-only pg_rewind, take 2  (Chris Travers <chris.travers@adjust.com>)
Responses Re: Data-only pg_rewind, take 2
Re: Data-only pg_rewind, take 2
List pgsql-hackers
On Sun, Mar 17, 2019 at 09:00:57PM +0800, Chris Travers wrote:
> I also added test cases and some docs.  I don't know if the docs are
> sufficient.  Feedback is appreciated.

To be honest, I don't think that this approach is a good idea per the
same reasons as mentioned the last time, as this can cause pg_rewind
to break if any newly-added folder in the data directory has
non-replaceable data which is needed at the beginning of recovery and
cannot be automatically rebuilt.  So that's one extra maintenance
burden to worry about.

Here is the reference of the last thread about the same topic:
https://www.postgresql.org/message-id/CAN-RpxD8Y7hMOjzd93hOqV6n8kPEo5cmW9gYm+8JirTPiFnmmQ@mail.gmail.com
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Offline enabling/disabling of data checksums
Next
From: David Rowley
Date:
Subject: Re: Performance issue in foreign-key-aware join estimation