From: Heikki Linnakangas <hlinnakangas@vmware.com>
To: sthomas@optionshouse.com
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Thinking About Correlated Columns (again)
Date: Wed, 15 May 2013 18:52:22 +0300
Message-ID: <5193AF36.3040409@vmware.com> (raw)
In-Reply-To: <5193AA62.2040700@optionshouse.com>
References: <5193AA62.2040700@optionshouse.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 15.05.2013 18:31, Shaun Thomas wrote:
> I've seen conversations on this since at least 2005. There were even
> proposed patches every once in a while, but never any consensus. Anyone
> care to comment?
Well, as you said, there has never been any consensus.
There are basically two pieces to the puzzle:
1. What metric do you use to represent correlation between columns?
2. How do use collect that statistic?
Based on the prior discussions, collecting the stats seems to be tricky.
It's not clear for which combinations of columns it should be collected
(all possible combinations? That explodes quickly...), or how it can be
collected without scanning the whole table.
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.
- Heikki
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: hlinnakangas@vmware.com, sthomas@optionshouse.com
Subject: Re: Thinking About Correlated Columns (again)
In-Reply-To: <5193AF36.3040409@vmware.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox