| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Adding deprecation notices to pgcrypto documentation |
| Date: | 2024-03-04 22:49:26 |
| Message-ID: | 20240304224926.GA3370508@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-03-04 22:53:09 | Re: Avoid is possible a expensive function call (src/backend/utils/adt/varlena.c) |
| Previous Message | Tom Lane | 2024-03-04 22:41:58 | Re: SLRU optimization - configurable buffer pool and partitioning the SLRU lock |