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 ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
