From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)svr1(dot)postgresql(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ... |
Date: | 2003-09-07 15:48:12 |
Message-ID: | 200309071548.h87FmCD06475@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Tom Lane wrote:
> CVSROOT: /cvsroot
> Module name: pgsql-server
> Changes by: tgl(at)svr1(dot)postgresql(dot)org 03/09/07 12:26:54
>
> Modified files:
> doc/src/sgml : runtime.sgml
> src/backend/optimizer/geqo: geqo_main.c
> src/backend/utils/misc: guc.c postgresql.conf.sample
> src/bin/psql : tab-complete.c
> src/include/optimizer: geqo.h
>
> Log message:
> 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.
Tom, I see 'set seed' works:
test=> set seed = 0;
SET
but where is it documented?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-09-07 16:00:36 | Re: pgsql-server/ oc/src/sgml/runtime.sgml rc/back ... |
Previous Message | Tom Lane | 2003-09-07 15:27:25 | pgsql-server/contrib/chkpass chkpass.c |