Re: disable and enable trigger all when a foreign keys - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: disable and enable trigger all when a foreign keys
Date
Msg-id 20190715160926.GA17140@alvherre.pgsql
Whole thread Raw
In response to Re: disable and enable trigger all when a foreign keys  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On 2019-Jul-12, Tom Lane wrote:

> The OP already found the best method to get out of this, which is to
> drop and re-add the FK constraint.  Adding the constraint will force
> a full verification scan, which is what you need here since there's
> no information available about which checks were missed.

Maybe it would make sense to be able to mark the FK as not validated, so
that you can apply ALTER CONSTRAINT ... VALIDATE.  Seems better than
DROP + ADD.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-general by date:

Previous
From: ROS Didier
Date:
Subject: migration of a logical replication configuration
Next
From: Adrian Klaver
Date:
Subject: Re: after restore the size of the database is increased