MIME-Version: 1.0
References: <E1vub8B-000rlS-05@gemulon.postgresql.org>
 <CAOYmi+=4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ@mail.gmail.com>
In-Reply-To: 
 <CAOYmi+=4QhCjssfNEoZVK8LPtWxnfkwT5p-PAeoxtG9gpNjqOQ@mail.gmail.com>
From: Jelte Fennema-Nio <postgres@jeltef.nl>
Date: Mon, 23 Feb 2026 23:24:34 +0100
Message-ID: 
 <CAGECzQSCd+zCc4p+wqC9dA6yw86dXdt=sd+i3toB66TAz60WvQ@mail.gmail.com>
Subject: Re: pgsql: libpq: Grease the protocol by default
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Jacob Champion <jchampion@postgresql.org>,
 pgsql-committers@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAGECzQSCd%2BzCc4p%2BwqC9dA6yw86dXdt%3Dsd%2Bi3toB66TAz60WvQ%40mail.gmail.com>
Precedence: bulk

On Mon, 23 Feb 2026 at 22:17, Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> So while this is kind of a nice result, in that it's correctly
> diagnosing the problem, I need to add max_protocol_version=3.0 to the
> connection strings for these upgrades during beta.

Two thoughts:
1. I think we might want the "This indicates a bug in either the
server being contacted..." note to be added to the error even if you
use 3.2/3.3/3.X. It seems pretty helpful in general. It would need a
bit fancier detection though, with strings to search for based on the
actual requested version.
2. Why only force max_protocol_version=3.0 for beta? It sounds like
this would also be an issue once we eventually bump the default
version.