public inbox for [email protected]  

help / color / mirror / Atom feed

From: David G. Johnston <[email protected]>
To: Álvaro Herrera <[email protected]>
Cc: Peter Smith <[email protected]>
Cc: Magnus Hagander <[email protected]>
Cc: David Rowley <[email protected]>
Cc: PostgreSQL Documentation <[email protected]>
Subject: Re: Lets prohibit predicting the future in the documentation.
Date: Mon, 4 Aug 2025 09:30:29 -0700
Message-ID: <CAKFQuwYvShKVN8gTJNA931_nWBd0+bq23gV83yi0vPYoTmWC3A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAKFQuwbfCk-bD_rbNbf9QURKw8p1n99YwZy+bhzcpH6nnWZ9_g@mail.gmail.com>
	<[email protected]>

On Monday, August 4, 2025, Álvaro Herrera <[email protected]> wrote:

> On 2025-Jul-31, David G. Johnston wrote:
>
> > > On Thu, Jul 31, 2025 at 8:05 PM Magnus Hagander <[email protected]>
> > > 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.

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Lets prohibit predicting the future in the documentation.
  In-Reply-To: <CAKFQuwYvShKVN8gTJNA931_nWBd0+bq23gV83yi0vPYoTmWC3A@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox