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

From Jelte Fennema-Nio
Subject Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Date
Msg-id CAGECzQQHJkzssOfkHDzQny9_s4cck=8-ecG2JELS0jVCd1fTiA@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  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
On Fri, 30 Jan 2026 at 20:14, David G. Johnston
<david.g.johnston@gmail.com> wrote:
> Definite screenshot-2 preference for me.  Though I do wonder just looking at the image whether the reserved stuff
evenneeds a table.  The first row is not even a parameter but a guideline, and the second pertains to testing which
seemslike it can be incorporated separately.  I'd either go for just one table or two separate tables but not the
combinedvariant in screenshot-1.  I'm not seeing an advantage to be gained by the integration. 

Agreed. I expect maybe we'll reserve more protocol extensions in the
future (either the improved grease, or when we'll stop supporting an
extension at some point).

Regarding _pq_.[name], I agree with David that I think it would be
better to make that part of the introductory paragraph.



pgsql-hackers by date:

Previous
From: Jelte Fennema-Nio
Date:
Subject: Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
Next
From: Andrei Lepikhov
Date:
Subject: Re: Is there value in having optimizer stats for joins/foreignkeys?