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

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Jelte Fennema-Nio <me(at)jeltef(dot)nl>
Cc: 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: 2025-10-31 22:52:10
Message-ID: CAOYmi+=ogAhXyHTw=f-Hxo=EtJXA8z+j_yqfyO5aCLu68eu5eg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 31, 2025 at 2:56 PM Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
> I quite like that idea! Although maybe not 7FFF, but 270F so that
> PQfullProtocolVersion returns 39999.

+1

> And I think it'd be good to also
> add a protocol option, like _pq_.test_protocol_breakage and fail the
> connection attempt client side if that does not get returned back as
> unsupported.

Yeah, I feel better signing on to a plan like this if we think the
breakage is likely to lead to a comprehensive fix for
NegotiateProtocolVersion (as opposed to "we greased this thing in 2025
and now this thing in 2026 and now...").

Thanks,
--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2025-10-31 22:54:28 Re: Updating IPC::Run in CI?
Previous Message Philip Alger 2025-10-31 22:29:19 Re: [PATCH] Add pg_get_type_ddl() to retrieve the CREATE TYPE statement