Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Date
Msg-id CAOYmi+=i4m_bf_8vYmsGKZ+4-AEHRrrL5CxrJJdv3tzBDNz-yg@mail.gmail.com
Whole thread Raw
In response to Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
List pgsql-hackers
On Tue, Aug 20, 2024 at 12:55 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> Another way of describing this guarantee: If a client connects using
> 3.8 and configures no protocol parameters, the client needs to handle
> anything 3.8 specific that the handshake requires (such as longer
> cancel token). But then after that handshake it can choose to send
> only 3.0 packets and expect to receive only 3.0 packets back.

That guarantee (if adopted) would also make it possible for my use
case to proceed correctly, since a libpq client can still speak 3.0
packets on the socket safely. But in that case, PQprotocolVersion
should keep returning 3, because there's an explicit reason to care
about the major version by itself.

--Jacob



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Taking into account syncrep position in flush_lsn reported by apply worker
Next
From: Alvaro Herrera
Date:
Subject: configure failures on chipmunk