Re: *_collapse_limit, geqo_threshold

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "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 15:40:50
Message-ID: 7544.1246981250@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> I cannot reasonably plan some queries with join_collapse_limit set to 20. At
> least not without setting the geqo limit very low and a geqo_effort to a low
> value.
> So I would definitely not agree that removing j_c_l is a good idea.

Can you show some specific examples? All of this discussion seems like
speculation in a vacuum ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-07-07 15:49:37 Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby
Previous Message Ms swati chande 2009-07-07 15:25:09 Fw: Problem with postgres/ createdb