Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uiy57-00142F-Fj for pgsql-docs@arkaria.postgresql.org; Mon, 04 Aug 2025 16:30:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uiy54-002p97-Sp for pgsql-docs@arkaria.postgresql.org; Mon, 04 Aug 2025 16:30:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uiy54-002p8z-M2 for pgsql-docs@lists.postgresql.org; Mon, 04 Aug 2025 16:30:34 +0000 Received: from mail-oo1-xc29.google.com ([2607:f8b0:4864:20::c29]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uiy52-000jN7-1I for pgsql-docs@lists.postgresql.org; Mon, 04 Aug 2025 16:30:34 +0000 Received: by mail-oo1-xc29.google.com with SMTP id 006d021491bc7-6198ece73e0so1075747eaf.1 for ; Mon, 04 Aug 2025 09:30:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1754325031; x=1754929831; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RCnsQNN5Wes26nmZxPlFaTyqVoH/Yvz1eNGrbZC9/Ek=; b=KTqcU8kE7qUveTqf6hizBn2tqZGGY3wVguoVE/lacuysEU/G0QZYkodSdXUwBldpUk 5SvS5tdQmItL1Iqaru2gbpDwJKV8+ESTxDXm8OS5qMd6fTFQn4cf1TZwHqT9COq7YMMn auwoco6Hj2QAJVve/4CjIKEhlQfdqOgUhOFwy+z8B15tjaBshGWzLlclUdvswir3SqI5 +HWBP7Hq5V+VlTUZNWWmKLgvMPec863zMNqlZyKFeJ/loguDCDRgbVkJMJqFBYZX1wyv ar3nKaXWT0gOfvnf8Qa3hsvomtc6o68j2gEwczRFBd6YATpeTdg6kkUbVlpQfTs11bBK HnQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1754325031; x=1754929831; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RCnsQNN5Wes26nmZxPlFaTyqVoH/Yvz1eNGrbZC9/Ek=; b=Y0Vc9QgZRhFRjNhLC3JeVQ+lCZIQ1U0/ddFMLEpQdtWAwGs95mjwd9v3+Vl3MExRES d0PuBmarPK6Ii0ShLUUDvyY06Ny6wn2wJUWDmUfYLCvCgvG82XNJnEz+xS2lmBwj4vj6 gUaB9HHXS2VCOsNo7rs4ioelE0t9nLvVHEtyk1rhA62tfWs9O/fM6erZ6KVLt5sqNf7R M8dk4M5/PudTWxt3fRIZkfoBV2nw6zGCOqV+xgsSZn1DOKpKtvvtz1NRpKEn4QoZjLz0 v4ND1fcA1rMVuhd89yYcpbp++LtxXZwiJi8eU/oERn+jorz7U2zzbywAWza3udgkxbxB JCnA== X-Forwarded-Encrypted: i=1; AJvYcCUlxc2SJ0kUgWN7350YEt6LBuEaFTsQPm5qrxt1TN4Ackbm5laEAetdnB5G7vCPlf1YbUxo3+MiouLU@lists.postgresql.org X-Gm-Message-State: AOJu0Ywgafxg215bHE+tI8D/MdsUnnINRbPAtvC4JApbPtc+MoABafz0 xRUnxb3iQGHgZpOtNLEpIYgzrY1nm3VKFRetrjapa/ebhtF4nZn5rdRziY3VAce2Y004KHMzgyp V/JXkFE6jrNztfvn/fdE1Y/ROSByu7dI= X-Gm-Gg: ASbGncvxmpncEKKSHIDoWIZa2IbUOdJZjYuU9TLbs4/fVn6GZ9D1t22ePNn4pJ9F7ed MZM0JHDX9B1hKcVybGD0ZDNQpireUZ62ZyQF7/UyFJuu2BM6Sk6ZgP02/zyB/tWsq6ZHKXzVjDg y5iETx1cVl37wyOByxm/yIcHcqqatV8auzsL/jioDfLon/SZXoI1OC7sxnT4tZKzhdwLiIIPEf3 vo+z9iyDATkqwKcctpeU/fnfcRyFf7ajQ0EagOkINtujA4exhQ= X-Google-Smtp-Source: AGHT+IH4LHiuYNc92njRQbmhjjgqN40JGe+E+FVr8GxIfjHhTJD4iCw5ObUnXxk6HCrkwq2M9Gs9f7n/4VY0ngGgUlA= X-Received: by 2002:a05:6820:992:b0:619:950f:2413 with SMTP id 006d021491bc7-619950f26a5mr4573139eaf.2.1754325030699; Mon, 04 Aug 2025 09:30:30 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:5e6:0:b0:5dc:d940:7893 with HTTP; Mon, 4 Aug 2025 09:30:29 -0700 (PDT) In-Reply-To: <202508041122.jvtae2whlxmu@alvherre.pgsql> References: <202508041122.jvtae2whlxmu@alvherre.pgsql> From: "David G. Johnston" Date: Mon, 4 Aug 2025 09:30:29 -0700 X-Gm-Features: Ac12FXwCBtoSt8ziovspRvAlSFsxmh8CgcjfXaYZ-Yq6DLk8ujJCXJbANTDN0Pc Message-ID: Subject: Re: Lets prohibit predicting the future in the documentation. To: =?UTF-8?Q?=C3=81lvaro_Herrera?= Cc: Peter Smith , Magnus Hagander , David Rowley , PostgreSQL Documentation Content-Type: multipart/alternative; boundary="0000000000004687e3063b8ca0be" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004687e3063b8ca0be Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, August 4, 2025, =C3=81lvaro Herrera wrote= : > On 2025-Jul-31, David G. Johnston wrote: > > > > On Thu, Jul 31, 2025 at 8:05=E2=80=AFPM Magnus Hagander > > > 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=E2=80=99m not saying it is wrong because it is impossible this will ever = be implemented. It=E2=80=99s wrong because after 7 years the probability of th= is 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 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=E2=80=99t like giving out false hope. I=E2=80=99m unable to jud= ge 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. --0000000000004687e3063b8ca0be Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, August 4, 2025, =C3=81lvaro Herrera <alvherre@kurilemu.de> wrote:
On 2025-Jul-31, David G. Johnston wrote:

> > On Thu, Jul 31, 2025 at 8:05=E2=80=AFPM 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=E2=80=99m not saying it is wr= ong because it is impossible this will ever be implemented. It=E2=80=99s wr= ong because after 7 years the probability of this being removed are somewhe= re near 5% which is =E2=80=9Cunlikely=E2=80=9D.=C2=A0 Had it been truly lik= ely it would have been done within a few years at worse, IMO.

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

I just don=E2=80=99t lik= e giving out false hope.=C2=A0 I=E2=80=99m unable to judge how much that ha= rms people in this situation though.=C2=A0 And given how nitpicky we tend t= o get on clarity and succinctness in other aspects of the documentation hav= ing this seeming surpurflous and misleading sentence present seem to go aga= inst the grain.

David J.

--0000000000004687e3063b8ca0be--