Re: *_collapse_limit, geqo_threshold

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: "Dimitri Fontaine" <dim(at)hi-media(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: *_collapse_limit, geqo_threshold
Date: 2009-07-07 20:03:21
Message-ID: 4A5363B902000025000284FB@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> if we think it's reasonable for people to want to explicitly specify
> the join order

Regardless of the syntax (GUC or otherwise), that is an optimizer
hint. I thought we were trying to avoid those.

Although -- we do have all those enable_* GUC values which are also
optimizer hints; perhaps this should be another of those?
enable_join_reorder?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-07-07 20:05:33 Re: [HACKERS] commitfest.postgresql.org
Previous Message Dimitri Fontaine 2009-07-07 20:01:57 Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby