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.
