Could you please add some justification here? Note that we already have UNIQUE constraint over all partitions.

My primary concerns:
1) Global indexes allow for fast partition pruning. This means we no longer have the UNION ALL type of behavior for queries without partition keys and can rely on indexed columns to choose the correct partitions and provide a significant boost for read performance.
2) This makes implementing foreign keys on partitioned tables better

Sergei, I thought UNIQUE was not possible unless the "partition key" was included in the UNIQUEness constraint.

I agree that a global index is helpful for pruning. For example, a "range" over a HASH partitioning must now check all partitions; a global index would make pruning easy and efficient. I believe that HASH never provides performance benefits. I don't think that adding global indexing will change my mind. Can anyone provide a performance benefit relative to removing PARTITION BY HASH from the table (and adjusting the indexes if necessary)?