From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
cc: Euler Taveira <euler.taveira@enterprisedb.com>,
        Peter Eisentraut <peter@eisentraut.org>
Subject: State of pg_createsubscriber
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3222277.1716139817.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sun, 19 May 2024 13:30:17 -0400
Message-ID: <3222278.1716139817@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3222278.1716139817%40sss.pgh.pa.us>
Precedence: bulk

I'm fairly disturbed about the readiness of pg_createsubscriber.
The 040_pg_createsubscriber.pl TAP test is moderately unstable
in the buildfarm [1], and there are various unaddressed complaints
at the end of the patch thread (pretty much everything below [2]).
I guess this is good enough to start beta with, but it's far from
being good enough to ship, IMO.  If there were active work going
on to fix these things, I'd feel better, but neither the C code
nor the test script have been touched since 1 April.

			regards, tom lane

[1] https://buildfarm.postgresql.org/cgi-bin/show_failures.pl?max_days=3D3=
0&branch=3DHEAD&member=3D&stage=3Dpg_basebackupCheck&filter=3DSubmit
[2] https://www.postgresql.org/message-id/flat/3fa9ef0f-b277-4c13-850a-8cc=
c04de1406%40eisentraut.org#152dacecfc8f0cf08cbd8ecb79d6d38f