NikhilS wrote: > We will not (I know its a hard thing to do :) ), the intention is to > use this information from the parent and make it a property of the > child table. This will avoid the step for the user having to manually > specify CREATE INDEX and the likes on all the children tables > one-by-one.
But when I say CREATE TABLE ( a int PRIMARY KEY, ... ) PARTITION blah ... then I expect that the primary key will be enforced across all partitions. We currently sidestep that issue by not offering seemingly transparent partitioning. But if you are planning to offer that, the unique index issue needs to be solved, and I see nothing in your plan about that. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster
