From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] 6.5 cvs: can't drop table |
Date: | 1999-05-25 15:10:16 |
Message-ID: | 199905251510.LAA16124@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Oleg Bartunov <oleg(at)sai(dot)msu(dot)su> writes:
> > today I did some tests with current 6.5 from cvs and multiple joins.
> > I did unpredictable server crashes, i.e. sometimes query works
> > sometimes crashes.
>
> I have a theory about why the results are random: the GEQO planner
> deliberately uses random numbers to generate plans, so you don't
> always get the same plan out of it. Whatever bug you are seeing
> occurs only for a particular plan path. (I haven't had any luck
> repeating your crash here, so the bug may be platform-specific.)
>
> It bothers me that the GEQO results are not reliably reproducible
> across platforms; that complicates debugging. I have been thinking
> about suggesting that we ought to change GEQO to use a fixed random
> seed value by default, with the variable random seed being available
> only as a *non default* option. Comments anyone?
I would leave the random alone. There may be some advantages to having
it random.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | ZEUGSWETTER Andreas IZ5 | 1999-05-25 15:23:06 | AW: [HACKERS] 6.5 cvs: can't drop table |
Previous Message | Bruce Momjian | 1999-05-25 15:07:34 | Re: [HACKERS] Call for updates! |