State of pg_createsubscriber

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Euler Taveira <euler(dot)taveira(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: State of pg_createsubscriber
Date: 2024-05-19 17:30:17
Message-ID: 3222278.1716139817@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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=30&branch=HEAD&member=&stage=pg_basebackupCheck&filter=Submit
[2] https://www.postgresql.org/message-id/flat/3fa9ef0f-b277-4c13-850a-8ccc04de1406%40eisentraut.org#152dacecfc8f0cf08cbd8ecb79d6d38f

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira 2024-05-19 17:49:22 Re: State of pg_createsubscriber
Previous Message Tom Lane 2024-05-19 16:21:07 Re: [PATCH] Avoid mixing custom and OpenSSL BIO functions