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

From Tom Lane
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id 9974.1246988744@sss.pgh.pa.us
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  (Greg Stark <gsstark@mit.edu>)
Responses Re: *_collapse_limit, geqo_threshold  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Greg Stark <gsstark@mit.edu> writes:
> We should benchmark the planner on increasingly large sets of
> relations on a typical developer machine and set geqo to whatever
> value the planner can handle in that length of time. I suspect even at
> 10s you're talking about substantially larger values than the current
> default.

The problem is to find some realistic "benchmark" cases.  That's one
reason why I was pestering Andreas to see his actual use cases ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: New types for transparent encryption
Next
From: Simon Riggs
Date:
Subject: Re: WIP: generalized index constraints