| From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Markus Schiltknecht" <markus(at)bluegap(dot)ch> |
| Cc: | "NikhilS" <nikkhils(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Auto Partitioning |
| Date: | 2007-04-04 15:07:51 |
| Message-ID: | 1175699272.3623.171.camel@silverbirch.site |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Wed, 2007-04-04 at 16:31 +0200, Markus Schiltknecht wrote:
> But how to create an (unique) index which is completely different from
> the partitioning key?
Don't?
Most high volume tables are Fact tables with potentially more than 1 row
per Object/Dimension, so the unique index isn't appropriate in those
cases.
When partitioning a Major Entity its much easier to regard the PK as the
partitioning key + unique key, which is frequently possible, even if it
does break the exhortation against intelligent keys.
I wouldn't stand in the way of someone trying to add that functionality,
but I would describe the use case as fairly narrow.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-04-04 15:11:20 | Re: Bug in UTF8-Validation Code? |
| Previous Message | Tom Lane | 2007-04-04 15:01:48 | Re: IDENTITY/GENERATED v36 Re: Final version of IDENTITY/GENERATED patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zoltan Boszormenyi | 2007-04-04 15:19:02 | Re: IDENTITY/GENERATED v36 Re: Final version of IDENTITY/GENERATED patch |
| Previous Message | Tom Lane | 2007-04-04 15:01:48 | Re: IDENTITY/GENERATED v36 Re: Final version of IDENTITY/GENERATED patch |