Horton
Menu

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

Andres Freund <andres@anarazel.de>

View thread
From: Andres Freund <andres@anarazel.de>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, Robert Haas <robertmhaas@gmail.com>
Date: 2026-01-14T21:43:39Z
Lists: pgsql-hackers 
On 2026-01-14 12:23:24 -0800, Jacob Champion wrote:
> On Mon, Nov 3, 2025 at 7:42 AM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> > The negotiation does not require a separate roundtrip, only a tiny
> > additional message sent by the server. So I'm not worried about that
> > resulting in a measurable perf change. And even if there is one in
> > some super extreme benchmark, then you can still set
> > max_protocol_version=3.0 to revert to the regular behaviour.
> 
> Andres, should I take from the silence that you're satisfied with that?

My concern about that aspect has been ameliorated, I have however not
looked/thought about anything else in this proposal.

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