On Fri, Aug 16, 2024 at 10:37 AM Heikki Linnakangas <hlinn...@iki.fi> wrote: > If we envision accepting ranges like that in the future, it would be > good to do now rather than later. Otherwise, if someone wants to require > features from protocol 3.2 today, they will have to put > "protocol_version=3.2" in the connection string, and later when 3.3 > version is released, their connection string will continue to force the > then-old 3.2 version.
I'm totally cool with doing it now rather than later if you or someone else is willing to do the work. But I don't see why we'd need a protocol bump to change it later. If you write protocol_version=3.7 or protocol_version=3.2-3.7 we send the same thing to the server either way. It's only a difference in whether we slam the connection shut if the server comes back and say it can only do 3.0. > I'll split this patch like that, to make it easier to compare and merge > with Jelte's corresponding patches. That sounds great. IMHO, comparing and merging the patches is the next step here and would be great to see. -- Robert Haas EDB: http://www.enterprisedb.com
