Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Date
Msg-id CAOYmi+=5dSN6waSUDKEbbH82XQ+oqR7U_xYHVW_xXUR5Ta2h9Q@mail.gmail.com
Whole thread Raw
In response to Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
List pgsql-hackers
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

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Refactor how we form HeapTuples for CatalogTuple(Insert|Update)
Next
From: "David G. Johnston"
Date:
Subject: Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta