Re: *_collapse_limit, geqo_threshold - Mailing list pgsql-hackers

From Tom Lane
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id 10841.1247089562@sss.pgh.pa.us
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: *_collapse_limit, geqo_threshold
Re: *_collapse_limit, geqo_threshold
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> For a moment it seemed logical to suggest a session GUC for the seed,
> so if you got a bad plan you could keep rolling the dice until you got
> one you liked; but my right-brain kept sending shivers down my spine
> to suggest just how uncomfortable it was with that idea....

If memory serves, we actually had exactly that at some point.  But I
think the reason it got taken out was that it interfered with the
behavior of the random() function for everything else.  We'd have to
give GEQO its own private random number generator.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: *_collapse_limit, geqo_threshold
Next
From: Kasia Tuszynska
Date:
Subject: modules missing from Application Stack Wizard?