Re: Removing --disable-strong-random from the code
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>,
Heikki Linnakangas <hlinnaka@iki.fi>
Date: 2018-12-30T06:45:42Z
Lists: pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes: > Attached is a patch to clean up the code, which removes all the code > specific to random generation for backends (no more shmem code paths > and such), as well as the pg_frontend_random() and > pg_backend_random(). Thoughts or opinions? Hah, I was just about to work on that myself --- glad I didn't get to it quite yet. A couple of thoughts: 1. Surely there's documentation about --disable-strong-random to clean up too? 2. I wonder whether it's worth adding this to port.h: extern bool pg_strong_random(void *buf, size_t len); +/* pg_backend_random used to be a wrapper for pg_strong_random */ +#define pg_backend_random pg_strong_random to prevent unnecessary breakage in extensions that might be depending on pg_backend_random. 3. Didn't look, but the MSVC build code might need a tweak too now that pg_strong_random.o is built-always rather than conditional? regards, tom lane
Commits
-
Remove configure switch --disable-strong-random
- 1707a0d2aa6b 12.0 landed
-
Fix generation of padding message before encrypting Elgamal in pgcrypto
- 962da60591df 10.7 landed
- 2882bab920a4 11.2 landed
- d880b208e5fc 12.0 landed