Re: Lets prohibit predicting the future in the documentation. - Mailing list pgsql-docs

From David G. Johnston
Subject Re: Lets prohibit predicting the future in the documentation.
Date
Msg-id CAKFQuwYvShKVN8gTJNA931_nWBd0+bq23gV83yi0vPYoTmWC3A@mail.gmail.com
Whole thread Raw
In response to Re: Lets prohibit predicting the future in the documentation.  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-docs
On Monday, August 4, 2025, Álvaro Herrera <alvherre@kurilemu.de> wrote:
On 2025-Jul-31, David G. Johnston wrote:

> > On Thu, Jul 31, 2025 at 8:05 PM Magnus Hagander <magnus@hagander.net>
> > wrote:

> > > I can agree that the "will likely be removed" is a bad wording, and
> > > clearly it was wrong :)

I disagree that this was clearly wrong -- you just haven't seen that
future yet.

I’m not saying it is wrong because it is impossible this will ever be implemented. It’s wrong because after 7 years the probability of this being removed are somewhere near 5% which is “unlikely”.  Had it been truly likely it would have been done within a few years at worse, IMO.


We could change "will" to "might" or "may" or "could", but I think we
could also leave it well enough alone.  It doesn't actually hurt
anything, does it?

I just don’t like giving out false hope.  I’m unable to judge how much that harms people in this situation though.  And given how nitpicky we tend to get on clarity and succinctness in other aspects of the documentation having this seeming surpurflous and misleading sentence present seem to go against the grain.

David J.

pgsql-docs by date:

Previous
From: Álvaro Herrera
Date:
Subject: Re: further clarification: alter table alter column set not null - table scan is skipped
Next
From: Shuyu Pan
Date:
Subject: Re: further clarification: alter table alter column set not null - table scan is skipped