From: Tom Lane <tgl@sss.pgh.pa.us>
To: Magnus Hagander <magnus@hagander.net>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: hanefi.onaldi@microsoft.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Broken link in pgcrypto documentation
Date: Tue, 13 Feb 2024 14:42:36 -0500
Message-ID: <2666720.1707853356@sss.pgh.pa.us> (raw)
In-Reply-To: <CABUevEzOsYVQdqUPxwFhUZqkzTdn1dj1+mUF+cONKyETf+TcYQ@mail.gmail.com>
References: <170774255387.3279713.2822272755998870925@wrigleys.postgresql.org>
<6366A797-44A1-4685-A6BF-B2E5293C4321@yesql.se>
<CABUevEzOsYVQdqUPxwFhUZqkzTdn1dj1+mUF+cONKyETf+TcYQ@mail.gmail.com>
Magnus Hagander <magnus@hagander.net> writes:
> On Tue, Feb 13, 2024 at 7:12 PM Daniel Gustafsson <daniel@yesql.se> 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 what 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, magnus@hagander.net, daniel@yesql.se, hanefi.onaldi@microsoft.com, pgsql-docs@lists.postgresql.org
Subject: Re: Broken link in pgcrypto documentation
In-Reply-To: <2666720.1707853356@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox