MIME-Version: 1.0
From: RKN Sai Krishna <rknsaiforpostgres@gmail.com>
Date: Fri, 4 Mar 2022 19:49:51 +0530
Message-ID: <CAMVpbFN7t031cZX8kiOGhb1SL6J7vFG3Pwag_XcCmOfodCLmQg@mail.gmail.com>
Subject: pg_rewind enhancements
To: pgsql-hackers@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000ec592505d9653533"
Archived-At: <https://www.postgresql.org/message-id/CAMVpbFN7t031cZX8kiOGhb1SL6J7vFG3Pwag_XcCmOfodCLmQg%40mail.gmail.com>
Precedence: bulk

--000000000000ec592505d9653533
Content-Type: text/plain; charset="UTF-8"

Hi,

While using pg_rewind, I found that it is a bit difficult to use pg_rewind
as it seems to copy even the configuration files and also remove some of
the files created on the old primary which may not be present on the new
primary. Similarly it copies files under the data directory of the new
primary which may not be needed or which possibly could be junk files.

I would propose to have a couple of new command line arguments to
pg_rewind. One, a comma separated list of files which should be preserved
on the old primary, in other words which shouldn't be overwritten from the
new primary. Second, a comma separated list of files which should be
excluded while copying files from the new primary onto the old primary.

Would like to invite more thoughts from the hackers.

Regards,
RKN

--000000000000ec592505d9653533
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<br><br>While using pg_rewind, I found that it is a bit=
 difficult to use pg_rewind as it seems to copy even the configuration file=
s and also remove some of the files created on the old primary which may no=
t be present on the new primary. Similarly it copies files under the data d=
irectory of the new primary which may not be needed or which possibly could=
 be junk files.<br><br>I would propose to have a couple of new command line=
 arguments to pg_rewind. One, a comma separated list of files which should =
be preserved on the old primary, in other words which shouldn&#39;t be over=
written from the new primary. Second, a comma separated list of files which=
 should be excluded while copying files from the new primary onto the old p=
rimary.<br><br>Would like to invite more thoughts from the hackers.<br><br>=
Regards,<br>RKN<br></div>

--000000000000ec592505d9653533--