| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Peter Smith <smithpb2250(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Documentation <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Lets prohibit predicting the future in the documentation. |
| Date: | 2025-09-08 15:35:21 |
| Message-ID: | CA+TgmoZ=m2Lhi_8uvPJP3bo4S1qpHBV7WKsePmpDE6NAOEbTwQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Aug 4, 2025 at 12:30 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg | 2025-09-10 07:54:11 | Documentation improvement patch |
| Previous Message | Vik Fearing | 2025-09-08 07:30:37 | Re: SELECT List with/without parentheses |