Fix TRUNCATE .. CASCADE on partitions
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 7 Feb 2020 20:09:36 +0000 (17:09 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Fri, 7 Feb 2020 20:09:36 +0000 (17:09 -0300)
commit9710d3d4a87f428a10f63015a0d75ccf028dd137
treeaee0aa98a33841a09d55f28cad6ea52667b4d0dc
parentcb5b28613d553b1c750622e91cbc96c83f052a63
Fix TRUNCATE .. CASCADE on partitions

When running TRUNCATE CASCADE on a child of a partitioned table
referenced by another partitioned table, the truncate was not applied to
partitions of the referencing table; this could leave rows violating the
constraint in the referencing partitioned table.  Repair by walking the
pg_constraint chain all the way up to the topmost referencing table.

Note: any partitioned tables containing FKs that reference other
partitioned tables should be checked for possible violating rows, if
TRUNCATE has occurred in partitions of the referenced table.

Reported-by: Christophe Courtois
Author: Jehan-Guillaume de Rorthais
Discussion: http://postgr.es/m/20200204183906.115f693e@firost
doc/src/sgml/ref/truncate.sgml
src/backend/catalog/heap.c
src/test/regress/expected/truncate.out
src/test/regress/sql/truncate.sql