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 1vBuQw-006jYl-GR for pgsql-www@arkaria.postgresql.org; Thu, 23 Oct 2025 12:28:45 +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 1vBuQu-008YcZ-Et for pgsql-www@arkaria.postgresql.org; Thu, 23 Oct 2025 12:28:43 +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 1vBuQu-008YcO-8S for pgsql-www@lists.postgresql.org; Thu, 23 Oct 2025 12:28:43 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vBuQq-003nqq-2n for pgsql-www@lists.postgresql.org; Thu, 23 Oct 2025 12:28:42 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 2740F42A165 for ; Thu, 23 Oct 2025 14:28:40 +0200 (CEST) Received: from s981.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 12AC942CD42; Thu, 23 Oct 2025 14:28:40 +0200 (CEST) Received: from s473.loopia.se (unknown [172.22.191.6]) by s981.loopia.se (Postfix) with ESMTP id 0EE7822B1760; Thu, 23 Oct 2025 14:28:40 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s473.loopia.se (amavisd-new); dkim=pass (2048-bit key) header.d=yesql.se Received: from s934.loopia.se ([172.22.191.6]) by s473.loopia.se (s473.loopia.se [172.22.190.13]) (amavisd-new, port 10024) with LMTP id IoO8Wg09ifCX; Thu, 23 Oct 2025 14:28:39 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s934.loopia.se (Postfix) with ESMTPSA id 85C937CEA90; Thu, 23 Oct 2025 14:28:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1761222519; bh=HU66lewLt1cVqXjXMj9ZMQexT95NLnaTjicugC323Po=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=NQbzn989DcGR7SwGosN5jYlOLzVW0bLYnEqU8X01qeDgaILhStEYk0m+Sep1tRrH0 Gu/asYiALFtTg0NTXYTOxpd9dVuLo5G8JN5Q9lbC43vmR7QSUHo82r3ybEXJRPvwFu 39/ERn6D2v5HdvM8rlfhmIwFJbTByT6SHRflAC3c8k/DZKnOCIi1ncOefUmlahQF1W fYTx7NpqQPSvbox4+UFzPEb3eMmnLpEbRxgyb9DQ+ulo6IJo5gsrN2QgtjHVcNXa2S iROgJvkwHrwlYgbD2rFV3XEfRxFw4JVZSeCIm3DPaKEiytlS6vuUS/LNi4g8Mh+2ez +O1KCEWLs43zw== 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 In-Reply-To: Date: Thu, 23 Oct 2025 14:28:29 +0200 Cc: pgsql-www@lists.postgresql.org, Magnus Hagander Content-Transfer-Encoding: quoted-printable Message-Id: References: <0781CAB9-187C-42C6-BB66-F82F66591F92@yesql.se> <13E61A7B-D329-4187-B351-4698912255FD@yesql.se> <82C35F30-1559-4C7F-9E27-1E3177F457A2@yesql.se> To: David Rowley X-Mailer: Apple Mail (2.3776.700.51.11.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 22 Oct 2025, at 01:56, David Rowley wrote: >=20 > On Wed, 22 Oct 2025 at 01:09, Daniel Gustafsson = wrote: >> 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 >> On top of that, a few links in the descriptions were not markdown = encoded and >> thus rendered as plain text. >>=20 >> The attached v3 fixes these in 0003 and 0004. >=20 > * The new link seems dead. Looks like it should be > https://www.postgresql.org/docs/current/brin.html#BRIN-INTRO Indeed, fixed. > * Looks like this will cause issues as "current" moves forward in > versions and we add new sections before this: >=20 > - url: = https://www.postgresql.org/docs/16/functions-aggregate.html#id-1.5.8.27.5.= 2.4.1.1.1.1 > + url: = https://www.postgresql.org/docs/current/functions-aggregate.html#id-1.5.8.= 27.6.2.4.1.1.1.1 >=20 > If I adjust /current/ to /17/ it works, but not before then. Is there > anything more future proof we can do there? Adding anchors with indexterms, as you mention downthread, to anything = in the featurematrix is the solution to providing stable links. A manual step = of verifying links at time of GA is another option, which is probably a = good idea regardless. > Going back to /14/ that links to left() instead of casefold(). Right, but that's only if you edit the url and I don't think we can ever protect ourselves from users manually testing links. If you go to the = above page and click on the link for v14 documentation it won't use the anchor = and thus works. > * The following no longer links to where it intended to: >=20 > - url: = https://www.postgresql.org/docs/current/static/collation.html#id-1.6.10.4.= 5.7.5 > + url: = https://www.postgresql.org/docs/current/collation.html#id-1.6.10.4.5.7.5 >=20 > i.e basically someone made the same mistake as the above ones were > about to make. Interesting, the history of that edit is lost as it was done when the = matrix was defined in the database and not in a standalone yaml file. The = correct link seems to be: = https://www.postgresql.org/docs/current/collation.html#ICU-CUSTOM-COLLATIO= NS -- Daniel Gustafsson