Horton

Re: creating CHECK constraints as NOT VALID

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Ross J. Reedstrom <reedstrm@rice.edu>
Cc: Kevin Grittner <kevin.grittner@wicourts.gov>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-05-31T20:07:03Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix pg_get_constraintdef to cope with NOT VALID constraints

Excerpts from Ross J. Reedstrom's message of mar may 31 14:02:04 -0400 2011:

> Follows from one of the practical maxims of databases: "The data is
> always dirty" Being able to have the constraints enforced at least for
> new data allows you to at least fence the bad data, and have a shot at
> fixing it all. Right now, you may be forced into running with
> constraints effectively 'off', depending on the app to get new data
> right, while attempting to catch up. And the app probably put the bad
> data in there in the first place. One of the thankless, important but
> seemingly never urgent tasks.

Interesting point of view.  I have to admit that I didn't realize I was
allowing that, even though I have wished for it in the past myself.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support