| From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Thinking About Correlated Columns (again) |
| Date: | 2013-05-15 16:27:29 |
| Message-ID: | 5193B771.70502@optionshouse.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 05/15/2013 10:52 AM, Heikki Linnakangas wrote:
> I think it would be pretty straightforward to use such a statistic,
> once we have it. So perhaps we should get started by allowing the DBA
> to set a correlation metric manually, and use that in the planner.
The planner already kinda does this with functional indexes. It would
definitely be nice to override the stats with known correlations when
possible.
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-05-15 16:39:46 | Re: Thinking About Correlated Columns (again) |
| Previous Message | Craig James | 2013-05-15 16:23:07 | Re: Thinking About Correlated Columns (again) |