Re: Adding deprecation notices to pgcrypto documentation - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Adding deprecation notices to pgcrypto documentation
Date
Msg-id 20240304224926.GA3370508@nathanxps13
Whole thread Raw
In response to Re: Adding deprecation notices to pgcrypto documentation  (Daniel Gustafsson <daniel@yesql.se>)
Responses Re: Adding deprecation notices to pgcrypto documentation
List pgsql-hackers
On Mon, Mar 04, 2024 at 10:03:13PM +0100, Daniel Gustafsson wrote:
> Cleaning out my inbox I came across this which I still think is worth doing,
> any objections to going ahead with it?

I think the general idea is reasonable, but I have two small comments:

* Should this be a "Warning" and/or moved to the top of the page?  This
  seems like a relatively important notice that folks should see when
  beginning to use pgcrypto.

* Should we actually document the exact list of algorithms along with
  detailed reasons?  This list seems prone to becoming outdated.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock
Next
From: Michael Paquier
Date:
Subject: Re: Avoid is possible a expensive function call (src/backend/utils/adt/varlena.c)