MIME-Version: 1.0
References: 
 <CAKFQuwbfCk-bD_rbNbf9QURKw8p1n99YwZy+bhzcpH6nnWZ9_g@mail.gmail.com>
 <202508041122.jvtae2whlxmu@alvherre.pgsql>
 <CAKFQuwYvShKVN8gTJNA931_nWBd0+bq23gV83yi0vPYoTmWC3A@mail.gmail.com>
In-Reply-To: 
 <CAKFQuwYvShKVN8gTJNA931_nWBd0+bq23gV83yi0vPYoTmWC3A@mail.gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
Date: Mon, 8 Sep 2025 11:35:21 -0400
Message-ID: 
 <CA+TgmoZ=m2Lhi_8uvPJP3bo4S1qpHBV7WKsePmpDE6NAOEbTwQ@mail.gmail.com>
Subject: Re: Lets prohibit predicting the future in the documentation.
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: =?UTF-8?Q?=C3=81lvaro_Herrera?= <alvherre@kurilemu.de>,
	Peter Smith <smithpb2250@gmail.com>, Magnus Hagander <magnus@hagander.net>,
	David Rowley <dgrowleyml@gmail.com>,
	PostgreSQL Documentation <pgsql-docs@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CA%2BTgmoZ%3Dm2Lhi_8uvPJP3bo4S1qpHBV7WKsePmpDE6NAOEbTwQ%40mail.gmail.com>
Precedence: bulk

On Mon, Aug 4, 2025 at 12:30=E2=80=AFPM David G. Johnston
<david.g.johnston@gmail.com> wrote:
> I=E2=80=99m not saying it is wrong because it is impossible this will eve=
r be implemented. It=E2=80=99s wrong because after 7 years the probability =
of this being removed are somewhere near 5% which is =E2=80=9Cunlikely=E2=
=80=9D.  Had it been truly likely it would have been done within a few year=
s 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.

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