Horton
Menu

Re: Executing pg_createsubscriber with a non-compatible control file

Michael Banck <mbanck@gmx.net>

View thread
From: Michael Banck <mbanck@gmx.net>
To: Michael Paquier <michael@paquier.xyz>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Euler Taveira <euler@eulerto.com>
Date: 2025-10-20T08:35:49Z
Lists: pgsql-hackers 
On Mon, Oct 20, 2025 at 09:54:52AM +0900, Michael Paquier wrote:
> On Sat, Oct 18, 2025 at 08:55:35AM +0900, Michael Paquier wrote:
> > With the addition of the version check in the binary, there is no
> > downside in documenting this requirement.
> 
> Okay, I have added a note about that in the docs, then applied your
> patch on HEAD.  Thanks!

Thank you!


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