Horton
Menu

Re: Executing pg_createsubscriber with a non-compatible control file

Michael Paquier <michael@paquier.xyz>

View thread
From: Michael Paquier <michael@paquier.xyz>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Euler Taveira <euler@eulerto.com>
Date: 2025-10-15T02:17:24Z
Lists: pgsql-hackers 
On Tue, Oct 14, 2025 at 11:54:26AM -0700, Masahiko Sawada wrote:
> All patches look good to me.

Thanks.  I have applied all that after a second look, not planning to
bother about the back branches for pg_createsubscriber.

We may be able to apply the version rules to more tools.  pg_checksums
and pg_rewind have hardcoded requirement based on PG_VERSION_NUM.  Not
sure if it's worth bothering about them, though.
--
Michael

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. pg_checksums: Use new routine to retrieve data of PG_VERSION

  2. pg_createsubscriber: Use new routine to retrieve data of PG_VERSION

  3. pg_resetwal: Use new routine to retrieve data of PG_VERSION

  4. pg_combinebackup: Use new routine to retrieve data of PG_VERSION

  5. pg_upgrade: Use new routine to retrieve data of PG_VERSION

  6. Introduce frontend API able to retrieve the contents of PG_VERSION