Horton

Re: creating CHECK constraints as NOT VALID

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: David Fetter <david@fetter.org>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-01T02:55: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 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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support