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

From Kevin Grittner
Subject Re: *_collapse_limit, geqo_threshold
Date
Msg-id 4A55AD15020000250002862C@gw.wicourts.gov
Whole thread Raw
In response to Re: *_collapse_limit, geqo_threshold  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> wrote:
> If, as you suggest, it isn't actually useful, then why keep it at
> all?
I was imagining that someone who has a query which is taking a long
time to run, and asserts that it would run faster if only the
optimizer would arrange the joins a certain way, could test that
theory, as part of the diagnostic process.  (In other words, for
similar reasons that the other enable_* GUC settings exist.)
I would certainly not want to use it in production, and wouldn't
expect that would normally be a very good idea.
-Kevin


pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: *_collapse_limit, geqo_threshold
Next
From: Andres Freund
Date:
Subject: Re: *_collapse_limit, geqo_threshold - example schema