postgresql/src/backend/access/common
Alvaro Herrera 897795240c Enable CHECK constraints to be declared NOT VALID
This means that they can initially be added to a large existing table
without checking its initial contents, but new tuples must comply to
them; a separate pass invoked by ALTER TABLE / VALIDATE can verify
existing data and ensure it complies with the constraint, at which point
it is marked validated and becomes a normal part of the table ecosystem.

An non-validated CHECK constraint is ignored in the planner for
constraint_exclusion purposes; when validated, cached plans are
recomputed so that partitioning starts working right away.

This patch also enables domains to have unvalidated CHECK constraints
attached to them as well by way of ALTER DOMAIN / ADD CONSTRAINT / NOT
VALID, which can later be validated with ALTER DOMAIN / VALIDATE
CONSTRAINT.

Thanks to Thom Brown, Dean Rasheed and Jaime Casanova for the various
reviews, and Robert Hass for documentation wording improvement
suggestions.

This patch was sponsored by Enova Financial.
2011-06-30 11:24:31 -04:00
..
heaptuple.c pgindent run before PG 9.1 beta 1. 2011-04-10 11:42:00 -04:00
indextuple.c pgindent run before PG 9.1 beta 1. 2011-04-10 11:42:00 -04:00
Makefile Remove cvs keywords from all files. 2010-09-20 22:08:53 +02:00
printtup.c Stamp copyrights for year 2011. 2011-01-01 13:18:15 -05:00
reloptions.c Pass collations to functions in FunctionCallInfoData, not FmgrInfo. 2011-04-12 19:19:24 -04:00
scankey.c Pass collations to functions in FunctionCallInfoData, not FmgrInfo. 2011-04-12 19:19:24 -04:00
tupconvert.c Stamp copyrights for year 2011. 2011-01-01 13:18:15 -05:00
tupdesc.c Enable CHECK constraints to be declared NOT VALID 2011-06-30 11:24:31 -04:00