Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta

Jacob Champion <jacob.champion@enterprisedb.com>

From: Jacob Champion <jacob.champion@enterprisedb.com>

To: Jelte Fennema-Nio <me@jeltef.nl>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, Robert Haas <robertmhaas@gmail.com>

Date: 2025-10-31T22:52:10Z

Lists: pgsql-hackers

On Fri, Oct 31, 2025 at 2:56 PM Jelte Fennema-Nio <me@jeltef.nl> wrote:
> I quite like that idea! Although maybe not 7FFF, but 270F so that
> PQfullProtocolVersion returns 39999.

+1

> 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.

Yeah, I feel better signing on to a plan like this if we think the
breakage is likely to lead to a comprehensive fix for
NegotiateProtocolVersion (as opposed to "we greased this thing in 2025
and now this thing in 2026 and now...").

Thanks,
--Jacob

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