From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Subject: | Re: Removing --disable-strong-random from the code |
Date: | 2018-12-30 06:45:42 |
Message-ID: | 23371.1546152342@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-12-30 07:15:49 | Re: Removing --disable-strong-random from the code |
Previous Message | Michael Paquier | 2018-12-30 06:32:19 | Removing --disable-strong-random from the code |