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 <postgres@jeltef.nl>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, Robert Haas <robertmhaas@gmail.com>
Date: 2026-02-18T23:27:14Z
Lists: pgsql-hackers
On Wed, Feb 18, 2026 at 3:11 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> I tried it out with PgBouncer commit f7ffd67ed8 (the one right before
> NegotiateProtocolVersion support was added) and got the following back
> with psql. So yes it works:

Cool! Thank you for testing that.

> I think "_pq_." would be very unlikely to cause false positives too
> *currently*, because it's the only protocol extension we're currently
> requesting. But I'm not sure that will remain true after we actually
> add support for some extensions (e.g. the error could be about an
> invalid option being used for a valid protocol extension). So I'd say
> let's stay on the "we're sure it's a bug" side and not use it as a
> heuristic.

Yeah, that makes sense. I plan to commit a squashed version of v8,
then, and if we think of improvements then we can always make them.

> I still have some not so secret hope that you (or another
> committer) will have time to look at my GoAway patch and realise it's
> pretty trivial and safe to commit.

(I will probably not be able to for the PG19 cycle.)

--Jacob



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. libpq: Grease the protocol by default

  2. libpq: Prepare for protocol grease during 19beta

  3. doc: Expand upon protocol versions and extensions

  4. libpq_pipeline: Test the default protocol version