Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
| От | Jelte Fennema-Nio | 
|---|---|
| Тема | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta | 
| Дата | |
| Msg-id | CAGECzQR9Yx484X7Kk+gdw5HPezvf4YWGg_GemqB2s6jWj2TCUg@mail.gmail.com обсуждение исходный текст  | 
		
| Ответ на | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta (Jacob Champion <jacob.champion@enterprisedb.com>) | 
| Ответы | 
                	
            		Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
            		
            		 | 
		
| Список | pgsql-hackers | 
On Fri, 31 Oct 2025 at 17:24, Jacob Champion <jacob.champion@enterprisedb.com> wrote: > I still wouldn't want the declaration > that "we default to the latest" to be mixed into the growing search > engine slop pile. Fair enough (although the intent is to get to that state at some point). > Is there an even stronger way for us to grease this? For example, > could we agree that no one will ever implement 0003.7FFF and push that > during the beta, failing if anyone gives us an unsupported version? I quite like that idea! Although maybe not 7FFF, but 270F so that PQfullProtocolVersion returns 39999. And I think it'd be good to also add a protocol option, like _pq_.test_protocol_breakage and fail the connection attempt client side if that does not get returned back as unsupported. I'll try to update this patch to do that in the coming days.
В списке pgsql-hackers по дате отправления: