Re: *_collapse_limit, geqo_threshold

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <gsstark(at)mit(dot)edu>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: *_collapse_limit, geqo_threshold
Date: 2009-07-07 17:56:15
Message-ID: 200907071956.15604.andres@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday 07 July 2009 19:45:44 Tom Lane wrote:
> Greg Stark <gsstark(at)mit(dot)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 ...
I will start writing a reduced/altered schema tomorrow then...

Andres

PS: Its "Andres" btw ;-)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-07-07 17:57:23 Re: WIP: generalized index constraints
Previous Message Simon Riggs 2009-07-07 17:47:17 Re: WIP: generalized index constraints