On 14/06/2011 01:11, Josh Berkus wrote:
Hmmm. Is this the behavior we want with NOT VALID constraints though?
I know that if I'm pouring 100m rows into a new partition as part of a
repartitioning scheme, I don't want to *ever* check them if I know
they're correct because of how I created the table (CREATE TABLE AS ...).
I can see why you would want that, but I'd say that's a separate feature
you need to explicitly request when creating the constraint. Consider
what happens in the "old data is garbage, but I want the new data to be
validated" use case if we allow constraint exclusion on NOT VALID
constraints.
--
Marko Tiikkaja http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
