| From: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Brown <time(at)bigpond(dot)net(dot)au>, Josh Berkus <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: multi-column index |
| Date: | 2005-03-17 11:18:28 |
| Message-ID: | i2pi31d7ea6qg67f5av9i7h0gscqk7tgjm@email.aon.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 17 Mar 2005 16:55:15 +0800, Christopher Kings-Lynne
<chriskl(at)familyhealth(dot)com(dot)au> wrote:
>Make it deal with cross-table fk correlations as well :)
That's a different story. I guess it boils down to cross-column
statistics for a single table. Part of this is the correlation between
values in two or more columns, which is not the same as the correlation
between column (or index tuple) values and tuple positions.
And yes, I did notice the smiley ;-)
Servus
Manfred
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2005-03-17 12:02:58 | 2 rows expected on a primary key |
| Previous Message | Daniel Schuchardt | 2005-03-17 09:37:05 | Re: cpu_tuple_cost |