aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/tqueue.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2017-07-03 12:10:11 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2017-07-03 12:10:11 +0300
commitbf723a274cbb00c7fba66c66312a77940af13d79 (patch)
tree92a84fb0c3060a9fbcbd90013cdaafdf44ec46d9 /src/backend/executor/tqueue.c
parent647675228f2b18964d8ade8a1061a719e527acfb (diff)
downloadpostgresql-bf723a274cbb00c7fba66c66312a77940af13d79.tar.gz
postgresql-bf723a274cbb00c7fba66c66312a77940af13d79.zip
Forbid gen_random_uuid() with --disable-strong-random
Previously, gen_random_uuid() would fall back to a weak random number generator, unlike gen_random_bytes() which would just fail. And this was not made very clear in the docs. For consistency, also make gen_random_uuid() fail outright, if compiled with --disable-strong-random. Re-word the error message you get with --disable-strong-random. It is also used by pgp functions that require random salts, and now also gen_random_uuid(). Reported by Radek Slupik. Discussion: https://www.postgresql.org/message-id/20170101232054.10135.50528@wrigleys.postgresql.org
Diffstat (limited to 'src/backend/executor/tqueue.c')
0 files changed, 0 insertions, 0 deletions