| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta |
| Date: | 2026-01-15 00:31:10 |
| Message-ID: | CAOYmi+=ZZ1XbBkDkWCJgmj-BN-aJ6o6OdgxQBifZE=sYr171xg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 14, 2026 at 2:56 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2026-01-15 00:42:00 | Re: Proposal to allow setting cursor options on Portals |
| Previous Message | Amit Langote | 2026-01-15 00:12:35 | Re: Segmentation fault on proc exit after dshash_find_or_insert |