| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Emanuel Araújo <eacshm(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: disable and enable trigger all when a foreign keys |
| Date: | 2019-07-15 16:09:26 |
| Message-ID: | 20190715160926.GA17140@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-07-15 17:07:51 | Re: after restore the size of the database is increased |
| Previous Message | ROS Didier | 2019-07-15 13:35:12 | migration of a logical replication configuration |