From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Mary Edie Meredith <maryedie(at)osdl(dot)org>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>, osdldbt-general <osdldbt-general(at)lists(dot)sourceforge(dot)net> |
Subject: | Re: [GENERAL] how to get accurate values in pg_statistic |
Date: | 2003-09-05 21:02:02 |
Message-ID: | 200309052102.h85L22818312@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > We do have:
> > #geqo_random_seed = -1 # -1 = use variable seed
>
> > that lets you force a specific random seed for testing purposes. I
> > wonder if that could be extended to control VACUUM radomization too.
> > Right now, it just controls GEQO and in fact gets reset on every
> > optimizer run.
>
> Actually, just the other day I was thinking we should take that out.
> Since there is only one random number generator in the C library,
> GEQO is messing with everyone else's state every time it decides to do
> an srandom(). And there is certainly no need to do an explicit srandom
> with a "random" seed every time through the optimizer, which is the
> code's default behavior at the moment. That just decreases the
> randomness AFAICS, compared to letting the established sequence run.
Agreed.
--
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 | Neil Conway | 2003-09-05 21:09:49 | Re: SELECT's take a long time compared to other DBMS |
Previous Message | Tom Lane | 2003-09-05 20:55:49 | Re: [GENERAL] how to get accurate values in pg_statistic |