From 48beecda7cbd2e73ebc11c88d3567ad064604bda Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 7 Sep 2003 15:26:54 +0000 Subject: Remove geqo_random_seed parameter. Having geqo reset the global random() sequence every time it's called is bogus --- it interferes with user control over the seed, and actually decreases randomness overall (because a seed based on time(NULL) is pretty predictable). If you really want a reproducible result from geqo, do 'set seed = 0' before planning a query. --- src/backend/utils/misc/postgresql.conf.sample | 1 - 1 file changed, 1 deletion(-) (limited to 'src/backend/utils/misc/postgresql.conf.sample') diff --git a/src/backend/utils/misc/postgresql.conf.sample b/src/backend/utils/misc/postgresql.conf.sample index a30ae074a18..c04aaab39bb 100644 --- a/src/backend/utils/misc/postgresql.conf.sample +++ b/src/backend/utils/misc/postgresql.conf.sample @@ -121,7 +121,6 @@ #geqo_generations = 0 #geqo_pool_size = 0 # default based on tables in statement, # range 128-1024 -#geqo_random_seed = -1 # -1 = use variable seed #geqo_selection_bias = 2.0 # range 1.5-2.0 # - Other Planner Options - -- cgit v1.2.3