Horton
Menu

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

David G. Johnston <david.g.johnston@gmail.com>

View thread
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, 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:13:44Z
Lists: pgsql-hackers 
On Fri, Jan 30, 2026 at 12:03 PM Jacob Champion <
jacob.champion@enterprisedb.com> wrote:

> 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.
>
>
Definite screenshot-2 preference for me.  Though I do wonder just looking
at the image whether the reserved stuff even needs a table.  The first row
is not even a parameter but a guideline, and the second pertains to testing
which seems like it can be incorporated separately.  I'd either go for just
one table or two separate tables but not the combined variant in
screenshot-1.  I'm not seeing an advantage to be gained by the integration.

David J.

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