PostgreSQL is famous for its data integrity, but as datasets grow into terabytes, the cost of maintaining that integrity can become a bottleneck. To solve this, PostgreSQL offers different "states" for constraints. While many are familiar with NOT VALID, a new concept from the SQL:2023 standard has entered the conversation: NOT ENFORCED, which has been officially added to PostgreSQL 18 . While they might sound similar, they serve very different roles in a database's lifecycle. TL;DR In PostgreSQL, constraints aren't always strictly "on" or "off". NOT VALID allows you to add a constraint to a
↧
