| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Ross J(dot) Reedstrom <reedstrm(at)rice(dot)edu> |
| Cc: | Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: creating CHECK constraints as NOT VALID |
| Date: | 2011-05-31 20:07:03 |
| Message-ID: | 1306872360-sup-3515@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-05-31 20:11:35 | Re: Getting a bug tracker for the Postgres project |
| Previous Message | Peter Eisentraut | 2011-05-31 19:38:08 | Re: Please test peer (socket ident) auth on *BSD |