On Tue, 20 Aug 2024 at 18:42, David G. Johnston
<david.g.johnston@gmail.com> wrote:
> v18 libpq-based clients, if they attempt to connect using v4 and fail, will try again using the v3 connection. That
willretain status quo behavior when something like a connection pooler doesn't understand the new reality.
Having connection latency double when connecting to an older Postgres
is something I'd very much like to avoid. Reconnecting functionally
retains the status quo, but it doesn't retain the expected perf
characteristics. By using a minor protocol version we can easily avoid
this connection latency issue.