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

From Kevin Grittner
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id 4A5363B902000025000284FB@gw.wicourts.gov
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  (Dimitri Fontaine <dfontaine@hi-media.com>)
Responses Re: *_collapse_limit, geqo_threshold  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: *_collapse_limit, geqo_threshold  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.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


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby
Next
From: Robert Haas
Date:
Subject: Re: [pgsql-www] commitfest.postgresql.org