On Mon, Apr 3, 2017 at 6:28 AM, Amit Langote <langote_amit...@lab.ntt.co.jp> wrote: > Since nowhere has the user asked to ensure unique(b) across partitions by > defining the same on parent, this seems just fine. But one question to > ask may be whether that will *always* be the case? That is, will we take > ON CONFLICT DO NOTHING without the conflict target specification to mean > checking for conflicts on the individual leaf partition level, even in the > future when we may have global constraints?
No. We'll take it to mean that there is no conflict with any unique constraint we're able to declare. Currently, that means a partition-local unique constraint because that's all there is. It will include any new things added in the future. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
