Re: pgsql: libpq: Grease the protocol by default
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>,
pgsql-hackers@lists.postgresql.org,
Andrew Dunstan <andrew@dunslane.net>,
Nathan Bossart <nathandbossart@gmail.com>
Date: 2026-02-24T18:50:33Z
Lists: pgsql-hackers
Jacob Champion <jacob.champion@enterprisedb.com> writes: > So pg_upgrade will use max_protocol_version=3.0 with all servers v10 > and below, in practice. There's nothing wrong with that behavior, but > I think I should switch to a simple `< 1100` check in the code to > avoid misleading people, unless anyone has a better way that won't > significantly increase the cost of the backport. Simple is good here. I don't think we'd buy much by distinguishing minor versions of already-EOL servers. Also, I suspect that pg_upgrade can't get the minor version except by starting the server and asking it --- we don't record anything but major version on-disk. regards, tom lane
Commits
-
pg_upgrade: Use max_protocol_version=3.0 for older servers
- c47744ede01c 14.23 landed
- e726620d208e 15.18 landed
- a38ed212ff23 16.14 landed
- ad7fc3f1f83f 17.10 landed
- 1b2773179f31 18.4 landed
- a60a103386a1 19 (unreleased) landed
-
libpq: Grease the protocol by default
- 4966bd3ed95e 19 (unreleased) cited
-
libpq: Prepare for protocol grease during 19beta
- d8d7c5dc8f74 19 (unreleased) cited