Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
| От | David G. Johnston |
|---|---|
| Тема | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs |
| Дата | |
| Msg-id | CAKFQuwZXJeKzq-a0ChL4oF105xu6T_BMZErcbNSvy_6VuYeMfQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs (Jacob Champion <jacob.champion@enterprisedb.com>) |
| Ответы |
Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
|
| Список | pgsql-hackers |
On Tue, Aug 20, 2024 at 10:31 AM Jacob Champion <jacob.champion@enterprisedb.com> wrote:
If we decide we can't, then so be it -- things will
break either way -- but it's still strange to me that we'd be okay
with literally zero forward compatibility and still call that a "minor
version".
Semantic versioning guidelines are not something we are following, especially here.
Our protocol version is really just two-part; just like our server major version used to be. We just happen to have named both parts here, unlike with the historical server major version.
We never have implemented a protocol change during a minor server version update, it doesn't have (though maybe it needs?) a patch version part.
David J.
В списке pgsql-hackers по дате отправления: