Horton
Menu

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

Jacob Champion <jacob.champion@enterprisedb.com>

View thread
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-30T19:03:04Z
Lists: pgsql-hackers

Attachments

On Fri, Jan 30, 2026 at 10:06 AM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> > 2. In my v5 I created a dedicated section header for protocol
> > extensions instead of including it in the extension. I think that's
> > slightly nicer, primarily so you can link to that section from the
> > StartupMessage docs (including the introductory paragraph), instead of
> > having to link to the table.
>
> Agreed, will fix.

Done in v6-0001. v6-0002/3 are the same as v5.

> As long as the consistency provides *clarity*, I'm fine with it; I'm
> just not sure that it does. I'll post a v6 with some screenshots.

screenshot-1.png shows what the combined table looks like under our
website CSS. The indent is still odd, but it looks less jarring when
"themed", IMHO.

v6-0004 is a squash commit that splits the table instead.
screenshot-2.png shows the effect of the split. I really don't like
it, but I won't die on that hill.

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