| From: | Piotr Stefaniak <postgres(at)piotr-stefaniak(dot)me> |
|---|---|
| To: | "dmigowski(at)ikoffice(dot)de" <dmigowski(at)ikoffice(dot)de>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14888: Need to recheck contraints |
| Date: | 2017-11-06 06:48:05 |
| Message-ID: | DB6PR0301MB23743D5463DD6B109FBF61BFF2500@DB6PR0301MB2374.eurprd03.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2017-11-06 06:50, dmigowski(at)ikoffice(dot)de wrote:
> The is no way to VALIDATE constraints that PostgreSQL already thinks of as
> VALID. I would love a "force" option here, because when disabling all
> triggers there is still the possibility for errors and I would love to check
> our databases for them.
>
> How do I do it?
This is a feature request, but I need it too.
My work-around is to use a DO statement that iterates over pg_constraint
to duplicate all interesting constraints giving each a new name and ends
with a RAISE EXCEPTION 'OK'. If the execution ends with that "error",
all constraints are valid. I guess you could wrap it into a BEGIN ...
ROLLBACK to get the same effect.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Migowski | 2017-11-06 06:50:17 | Re: BUG #14888: Need to recheck contraints |
| Previous Message | dmigowski | 2017-11-06 05:50:40 | BUG #14888: Need to recheck contraints |