Re: Optimizer oddness, possibly compounded in 8.1

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Hannu Krosing <hannu(at)skype(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Optimizer oddness, possibly compounded in 8.1
Date: 2005-12-07 01:46:57
Message-ID: 43963F11.9000101@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Glaesemann 2005-12-07 01:50:16 Re: Optimizer oddness, possibly compounded in 8.1
Previous Message Christopher Kings-Lynne 2005-12-07 01:43:30 Re: Oddity with extract microseconds?