Re: Optimizer oddness, possibly compounded in 8.1

Christopher Kings-Lynne <chriskl@familyhealth.com.au>

From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Simon Riggs <simon@2ndquadrant.com>
Cc: Hannu Krosing <hannu@skype.net>, Tom Lane <tgl@sss.pgh.pa.us>, Philip Warner <pjw@rhyme.com.au>, pgsql-hackers@postgresql.org
Date: 2005-12-07T01:46:57Z
Lists: pgsql-hackers
>>One of the easier cases would be non-overlapping (exclusive) constraints
>>on union subtables on the joined column.
>>
>>This could serve as a "partition key", or in case of many nonoverlapping
>>columns (ex.: table is partitioned by date and region), as many
>>partition keys.
> 
> 
> Yes, thats my planned direction.

In case you didn't know btw, MySQL 5.1 is out with rather extensive 
table partition support.  So get coding :D

Chris