| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: creating CHECK constraints as NOT VALID |
| Date: | 2011-06-01 02:55:03 |
| Message-ID: | 1306896838-sup-80@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from David Fetter's message of mar may 31 21:42:08 -0400 2011:
> A colleague brought up an interesting idea that I think is worth
> exploring for all NOT VALID constraints, to wit, is there some way
> (via SQL) to find which rows violate which constraints? I'm picturing
> some kind of function that could be aggregated into some structure for
> each violating row...
Seems like a job for a plpgsql function with a bunch of exception handlers ...
Some details like the violated constraint name would be hard to extract,
probably, though.
--
Á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 | Robert Haas | 2011-06-01 02:58:16 | Re: [PERFORM] Hash Anti Join performance degradation |
| Previous Message | Tom Lane | 2011-06-01 02:53:47 | Re: [BUGS] BUG #6046: select current_date crashes postgres |