Re: Executing pg_createsubscriber with a non-compatible control file

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Michael Banck <mbanck(at)gmx(dot)net>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Euler Taveira <euler(at)eulerto(dot)com>
Subject: Re: Executing pg_createsubscriber with a non-compatible control file
Date: 2025-10-20 00:54:52
Message-ID: aPWIXDpeuHSRTrrF@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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!

If others would like to apply the same kind of version checks in some
of the other in-core tools, please feel free to mention them here or
on a new thread.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-10-20 01:02:31 Re: [PATCH] Fix POSIX compliance in pgwin32_unsetenv()
Previous Message Michael Paquier 2025-10-20 00:50:53 Re: isolation tester limitation in case of multiple injection points in a single command