| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: proposal : cross-column stats |
| Date: | 2010-12-13 22:51:34 |
| Message-ID: | AANLkTi=dKS8vgD-t8YUSEk66JRXutXzObyUL1ax+uE26@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 13, 2010 at 5:45 PM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
>> I'll suggest again how to decide *which* columns to cross: whichever
>> columns are combined in composite indexes. In version 2, allow the DBA
>> to specify combinations.
> I think this is a bit early to discuss this, given the fact that we
> don't have a working solution yet.
Agreed. Not to mention that adding syntax is pretty easy. The hard
part is figuring out what data you want to collect and what you want
to do with it. If we can figure that out, the syntax will be simple
by comparison.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2010-12-13 22:52:28 | Transaction-scope advisory locks |
| Previous Message | Robert Haas | 2010-12-13 22:49:06 | Re: hstores in pl/python |