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: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
Heikki Linnakangas <hlinnaka@iki.fi>, Robert Haas <robertmhaas@gmail.com>
Date: 2026-01-15T00:31:10Z
Lists: pgsql-hackers
On Wed, Jan 14, 2026 at 2:56 PM Jacob Champion <jacob.champion@enterprisedb.com> wrote: > > I think max_protocol_version=grease makes a lot of sense. Because we > > really want to make it as easy as possible for people to try out their > > implementation of the negotation (see this for example[1]) > > Yeah, I'd like to have that ability too. I don't know that I can > commit to writing or reviewing that amount of code for 19, though. > (And maybe there are lessons we'll learn during beta that can inform a > better production feature?) Per offline confusion/discussion: I plan to work on a grease feature for beta _regardless_ of whether a "production-grade" max_protocol_version=grease option turns out to be viable before feature freeze; do not feel like you "have" to put work into the latter just to get the former. Sorry about that. --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