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

From David G. Johnston
Subject Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Date
Msg-id CAKFQuwbUNwHQjuTMKdL3g9EUkZWrX24r9ssrW5zjFMrg0FYyoQ@mail.gmail.com
Whole thread Raw
In response to Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs  (Jacob Champion <jacob.champion@enterprisedb.com>)
List pgsql-hackers
On Tue, Aug 20, 2024 at 10:46 AM Jacob Champion <jacob.champion@enterprisedb.com> wrote:
On Tue, Aug 20, 2024 at 10:42 AM David G. Johnston
<david.g.johnston@gmail.com> wrote:
> Semantic versioning guidelines are not something we are following, especially here.

I understand; the protocol is ours, and we'll do whatever we do in the
end. I'm claiming that we can choose to provide semantics, and if we
do, those semantics will help people who are not here on the list to
defend their use cases.


I was mostly just responding to your surprise given that we have a track-record here.  I agree that our existing effective policy isn't all that well documented, namely as to when the major component might change, and the fact that the minor component does not represent a "bug fix release".

David J.

pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Next
From: Tom Lane
Date:
Subject: Re: Improving the notation for ecpg.addons rules