public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Haas <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Á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, 8 Sep 2025 11:35:21 -0400
Message-ID: <CA+TgmoZ=m2Lhi_8uvPJP3bo4S1qpHBV7WKsePmpDE6NAOEbTwQ@mail.gmail.com> (raw)
In-Reply-To: <CAKFQuwYvShKVN8gTJNA931_nWBd0+bq23gV83yi0vPYoTmWC3A@mail.gmail.com>
References: <CAKFQuwbfCk-bD_rbNbf9QURKw8p1n99YwZy+bhzcpH6nnWZ9_g@mail.gmail.com>
	<[email protected]>
	<CAKFQuwYvShKVN8gTJNA931_nWBd0+bq23gV83yi0vPYoTmWC3A@mail.gmail.com>

On Mon, Aug 4, 2025 at 12:30 PM David G. Johnston
<[email protected]> wrote:
> 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.

I have mixed feelings about this particular example, but I agree that
it's best not to prognosticate about future feature development in the
docs, or even future deprecation. We're wrong A LOT when we do that.
It's best to just document what is and not what might be later.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

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], [email protected]
  Subject: Re: Lets prohibit predicting the future in the documentation.
  In-Reply-To: <CA+TgmoZ=m2Lhi_8uvPJP3bo4S1qpHBV7WKsePmpDE6NAOEbTwQ@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