aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-09-23 09:54:11 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-09-23 09:54:11 -0400
commitb251379fb44b4893624999f1ba00986c029f11cf (patch)
tree15f1c0f1a6383add79fe76487a9c75b5b8402bb3 /src/tutorial
parenta88fe25f50ae9ce491fe10a90aeef2cbed6f2b9a (diff)
downloadpostgresql-b251379fb44b4893624999f1ba00986c029f11cf.tar.gz
postgresql-b251379fb44b4893624999f1ba00986c029f11cf.zip
Avoid using PostmasterRandom() for DSM control segment ID.
Commits 470d886c3 et al intended to fix the problem that the postmaster selected the same "random" DSM control segment ID on every start. But using PostmasterRandom() for that destroys the intended property that the delay between random_start_time and random_stop_time will be unpredictable. (Said delay is probably already more predictable than we could wish, but that doesn't mean that reducing it by a couple orders of magnitude is OK.) Revert the previous patch and add a comment warning against misuse of PostmasterRandom. Fix the original problem by calling srandom() early in PostmasterMain, using a low-security seed that will later be overwritten by PostmasterRandom. Discussion: <20789.1474390434@sss.pgh.pa.us>
Diffstat (limited to 'src/tutorial')
0 files changed, 0 insertions, 0 deletions