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+=ZZ1XbBkDkWCJgmj-BN-aJ6o6OdgxQBifZE=sYr171xg@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>)
List pgsql-hackers
On Wed, Jan 14, 2026 at 2:56 PM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> > I think max_protocol_version=grease makes a lot of sense. Because we
> > really want to make it as easy as possible for people to try out their
> > implementation of the negotation (see this for example[1])
>
> Yeah, I'd like to have that ability too. I don't know that I can
> commit to writing or reviewing that amount of code for 19, though.
> (And maybe there are lessons we'll learn during beta that can inform a
> better production feature?)

Per offline confusion/discussion: I plan to work on a grease feature
for beta _regardless_ of whether a "production-grade"
max_protocol_version=grease option turns out to be viable before
feature freeze; do not feel like you "have" to put work into the
latter just to get the former. Sorry about that.

--Jacob



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Segmentation fault on proc exit after dshash_find_or_insert
Next
From: Jacob Champion
Date:
Subject: Re: Proposal to allow setting cursor options on Portals