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

From David G. Johnston
Subject Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Date
Msg-id CAKFQuwYZT9yaci3SyzezuAMhPY4Sn4zJy_L3-8jQQFpR=Gv2bw@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 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.

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Next
From: surya poondla
Date:
Subject: Re: log_min_messages per backend type