Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Jelte Fennema-Nio <me@jeltef.nl>
From: Jelte Fennema-Nio <me@jeltef.nl>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, Robert Haas <robertmhaas@gmail.com>
Date: 2025-10-31T21:56:19Z
Lists: pgsql-hackers
On Fri, 31 Oct 2025 at 17:24, Jacob Champion <jacob.champion@enterprisedb.com> wrote: > I still wouldn't want the declaration > that "we default to the latest" to be mixed into the growing search > engine slop pile. Fair enough (although the intent is to get to that state at some point). > Is there an even stronger way for us to grease this? For example, > could we agree that no one will ever implement 0003.7FFF and push that > during the beta, failing if anyone gives us an unsupported version? I quite like that idea! Although maybe not 7FFF, but 270F so that PQfullProtocolVersion returns 39999. And I think it'd be good to also add a protocol option, like _pq_.test_protocol_breakage and fail the connection attempt client side if that does not get returned back as unsupported. I'll try to update this patch to do that in the coming days.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
libpq: Grease the protocol by default
- 4966bd3ed95e 19 (unreleased) landed
-
libpq: Prepare for protocol grease during 19beta
- d8d7c5dc8f74 19 (unreleased) landed
-
doc: Expand upon protocol versions and extensions
- e3d37853ecd5 19 (unreleased) landed
-
libpq_pipeline: Test the default protocol version
- 9b9eaf08ab2d 19 (unreleased) landed