| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Dimitri Fontaine" <dim(at)hi-media(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: *_collapse_limit, geqo_threshold |
| Date: | 2009-07-09 13:40:53 |
| Message-ID: | 4A55AD15020000250002862C@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, 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-07-09 14:13:07 | Re: Re: Synch Rep: direct transfer of WAL file from the primary to the standby |
| Previous Message | Pavel Golub | 2009-07-09 12:52:05 | Re: bytea vs. pg_dump |