Re: Optimizer oddness, possibly compounded in 8.1 - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Optimizer oddness, possibly compounded in 8.1
Date
Msg-id 43963F11.9000101@familyhealth.com.au
Whole thread Raw
In response to Re: Optimizer oddness, possibly compounded in 8.1  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Optimizer oddness, possibly compounded in 8.1  (Michael Glaesemann <grzm@myrealbox.com>)
List 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



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Oddity with extract microseconds?
Next
From: Michael Glaesemann
Date:
Subject: Re: Optimizer oddness, possibly compounded in 8.1