On Tue, Feb 24, 2026 at 10:58 AM Jacob Champion <[email protected]> wrote: > We do store (the major version part of) `pg_ctl --version` at some > point, which we could improve upon, but I agree that adding additional > complexity here doesn't actually give us any benefit.
Okay, here are the patches I propose. The ones for 18-HEAD check for PG10 and below, and 14-17 additionally check that libpq >= 18, before adding max_protocol_version=3.0. I smoke-tested upgrades from 9.2, 10.1, and 11.0 for all six branches, and then re-ran that test matrix with pg_upgrade linked against a greased libpq. --Jacob
v2-0001-pg_upgrade-Use-max_protocol_version-3.0-for-older.patch
Description: Binary data
v2-0001-pg_upgrade-Use-max_protocol_version-3.0-for-older.18.patch
Description: Binary data
v2-0001-pg_upgrade-Use-max_protocol_version-3.0-for-older.17.patch
Description: Binary data
v2-0001-pg_upgrade-Use-max_protocol_version-3.0-for-older.16.patch
Description: Binary data
v2-0001-pg_upgrade-Use-max_protocol_version-3.0-for-older.15.patch
Description: Binary data
v2-0001-pg_upgrade-Use-max_protocol_version-3.0-for-older.14.patch
Description: Binary data
