Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\))
Subject: Re: Typos in the featurematrix
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <4cf3cbfb-4228-435f-a03d-f690fa8670be@postgresql.org>
Date: Thu, 23 Oct 2025 14:14:44 +0200
Cc: David Rowley <dgrowleyml@gmail.com>,
 pgsql-www@lists.postgresql.org,
 Magnus Hagander <magnus@hagander.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFBF4DCE-9D3E-4A5B-844E-79ABF9BC4295@yesql.se>
References: <0781CAB9-187C-42C6-BB66-F82F66591F92@yesql.se>
 <CAApHDvpOXAOPEhXRnWimyWmuRf+gN=yx22AoP_WM3aZ0M=n6Vw@mail.gmail.com>
 <13E61A7B-D329-4187-B351-4698912255FD@yesql.se>
 <82C35F30-1559-4C7F-9E27-1E3177F457A2@yesql.se>
 <4cf3cbfb-4228-435f-a03d-f690fa8670be@postgresql.org>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Archived-At: 
 <https://www.postgresql.org/message-id/EFBF4DCE-9D3E-4A5B-844E-79ABF9BC4295%40yesql.se>
Precedence: bulk

> On 23 Oct 2025, at 03:04, Jonathan S. Katz <jkatz@postgresql.org> =
wrote:

> * Going through 0001:
>=20
> -    description: automatic invalidation of cached exceutions plans
> +    description: automatic invalidation of cached executions plans
>=20
> should probably be "cached execution plans". Otherwise LGTM.

Fixed

> * Going through 0002:
>=20
> -  - name: IN/OUT/INOUT parameters for pl/pgsql and PL/SQL
> +  - name: IN/OUT/INOUT parameters for PL/pgSQL and PL/SQL
>=20
> We should probably not call it "PL/SQL" since it's not a procedural =
language. Perhaps:
>=20
> -  - name: IN/OUT/INOUT parameters for pl/pgsql and PL/SQL
> +  - name: IN/OUT/INOUT parameters for PL/pgSQL and SQL stored =
functions

Fixed

>> The featurematrix was a rabbithole that went deep, looking closer I =
realized
>> that links were using a variety of target versions: /current/, =
/devel/, or the
>> version which was current at the time of adding.  This means that for =
old
>> features we we still linking to the 9.x version of the docs, which =
clearly
>> isn't helpful to our users.  We also had quite a few /static/ links =
which 301
>> redirects since we don't have that level anymore.
>=20
> There were some reasons for this, the "version at the time of adding" =
ensuring that the links were accessible during the beta period (which =
also explained some of the /devel/, which I likely did). During the beta =
period, we'll still need to use the `/NN/` number so the links are =
accessible, but we can make it part of the procedure to more to =
`/current/` when we GA.

That makes a lot of sense.  We also need to use the /NN/ number for any =
feature
which is removed, to stabilise the link on the last version where it was
present.

Adding a "link-refresh" step to the GA checklist sounds like a good idea =
(and I
can volunteer to tackle it next time).

--
Daniel Gustafsson