Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
| От | Jacob Champion | 
|---|---|
| Тема | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta | 
| Дата | |
| Msg-id | CAOYmi+mKtB2V-8P7viTZDmWT0DXAz_NMYa38DjDDdE1LX_LMxQ@mail.gmail.com обсуждение исходный текст  | 
		
| Ответ на | libpq: Bump protocol version to version 3.2 at least until the first/second beta ("Jelte Fennema-Nio" <me@jeltef.nl>) | 
| Ответы | 
                	
            		Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta
            		
            		 | 
		
| Список | pgsql-hackers | 
On Thu, Oct 23, 2025 at 6:56 AM Jelte Fennema-Nio <me@jeltef.nl> wrote: > Depending on how this works in practice we'll likely still want to > revert this change before we actually release PG19. If we do that before > 19beta1 we still have roughly half a year where people will test the > ecosystem. I think the whole plan probably belongs in the user documentation. Even if no one were to read it, I still wouldn't want the declaration that "we default to the latest" to be mixed into the growing search engine slop pile. 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? --Jacob
В списке pgsql-hackers по дате отправления: