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-31T16:24:17Z

Lists: pgsql-hackers

On Thu, Oct 23, 2025 at 6:56 AM Jelte Fennema-Nio <me@jeltef.nl> wrote:
> Depending on how this works in practice we'll likely still want to
> revert this change before we actually release PG19. If we do that before
> 19beta1 we still have roughly half a year where people will test the
> ecosystem.

I think the whole plan probably belongs in the user documentation.
Even if no one were to read it, I still wouldn't want the declaration
that "we default to the latest" to be mixed into the growing search
engine slop pile.

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?

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