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 1rZyfy-007TB2-Ry for pgsql-docs@arkaria.postgresql.org; Tue, 13 Feb 2024 19:42:43 +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 1rZyfx-0024uy-4h for pgsql-docs@arkaria.postgresql.org; Tue, 13 Feb 2024 19:42:41 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rZyfw-0024um-Th for pgsql-docs@lists.postgresql.org; Tue, 13 Feb 2024 19:42:40 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rZyfu-006aiP-CR for pgsql-docs@lists.postgresql.org; Tue, 13 Feb 2024 19:42:39 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 41DJgaPo2666721; Tue, 13 Feb 2024 14:42:36 -0500 From: Tom Lane To: Magnus Hagander cc: Daniel Gustafsson , hanefi.onaldi@microsoft.com, pgsql-docs@lists.postgresql.org Subject: Re: Broken link in pgcrypto documentation In-reply-to: References: <170774255387.3279713.2822272755998870925@wrigleys.postgresql.org> <6366A797-44A1-4685-A6BF-B2E5293C4321@yesql.se> Comments: In-reply-to Magnus Hagander message dated "Tue, 13 Feb 2024 20:33:29 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <2666719.1707853356.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 13 Feb 2024 14:42:36 -0500 Message-ID: <2666720.1707853356@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Magnus Hagander writes: > On Tue, Feb 13, 2024 at 7:12=E2=80=AFPM Daniel Gustafsson wrote: >> However, I wonder if we aren't better off removing the "Useful Reading"= section >> altogether? The field of crypto is continuously advancing and keeping = a stale >> 10+ year old list of links is unlikely to provide more insights than wh= at more >> curated sites can do. > +1. I don't think it's the job of a postgres contrib module to maintain = that. +1. We haven't maintained that list in the past and it seems unlikely that we'll get better at it. I'm a little dubious about the "Technical References" list right below it, too. The RFC references are probably useful and stable, and maybe the wikipedia ref is OK, but I have little faith in either the stability or the long-term relevance of the other two links. regards, tom lane