Re: Thinking About Correlated Columns (again)
От
Shaun Thomas
Тема
Re: Thinking About Correlated Columns (again)
Дата
Msg-id
5193B771.70502@optionshouse.com
Ответ на
Re: Thinking About Correlated Columns (again) (Heikki Linnakangas)
Список
Дерево обсуждения
Thinking About Correlated Columns (again) Shaun Thomas <sthomas@optionshouse.com>
Re: Thinking About Correlated Columns (again) Heikki Linnakangas <hlinnakangas@vmware.com>
Re: Thinking About Correlated Columns (again) Shaun Thomas <sthomas@optionshouse.com>
Re: Thinking About Correlated Columns (again) Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: Thinking About Correlated Columns (again) Nikolas Everett <nik9000@gmail.com>
Re: Thinking About Correlated Columns (again) eggyknap <eggyknap@gmail.com>
Re: Thinking About Correlated Columns (again) Craig James <cjames@emolecules.com>
Re: Thinking About Correlated Columns (again) Andrew Dunstan <andrew@dunslane.net>
Re: Thinking About Correlated Columns (again) Gavin Flower <GavinFlower@archidevsys.co.nz>
Re: Thinking About Correlated Columns (again) Craig James <cjames@emolecules.com>
Re: Thinking About Correlated Columns (again) Thomas Kellerer <spam_eater@gmx.net>
Re: Thinking About Correlated Columns (again) Shaun Thomas <sthomas@optionshouse.com>
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@optionshouse.com ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
В списке pgsql-performance по дате отправления
