Invalidate partitions of table being attached/detached

Failing to do that, any direct inserts/updates of those partitions
would fail to enforce the correct constraint, that is, one that
considers the new partition constraint of their parent table.

Backpatch to 10.

Reported by: Hou Zhijie <[email protected]>
Author: Amit Langote <[email protected]>
Author: Álvaro Herrera <[email protected]>
Reviewed-by: Nitin Jadhav <[email protected]>
Reviewed-by: Pavel Borisov <[email protected]>
Discussion: https://postgr.es/m/OS3PR01MB5718DA1C4609A25186D1FBF194089%40OS3PR01MB5718.jpnprd01.prod.outlook.com

diff --git a/src/backend/commands/tablecmds.c b/src/backend/commands/tablecmds.c
index 1c2ebe1bf69537b65fa8a55ca91a57418d7aec76..14c8003535b83a64ae8841b151bcbfc8905221ae 100644 (file)
--- a/src/backend/commands/tablecmds.c
+++ b/src/backend/commands/tablecmds.c
@@ -17460,6 +17460,22 @@ ATExecAttachPartition(List **wqueue, Relation rel, PartitionCmd *cmd,
 
        ObjectAddressSet(address, RelationRelationId, RelationGetRelid(attachrel));
 
+       /*
+        * If the partition we just attached is partitioned itself, invalidate
+        * relcache for all descendent partitions too to ensure that their
+        * rd_partcheck expression trees are rebuilt; partitions already locked
+        * at the beginning of this function.
+        */
+       if (attachrel->rd_rel->relkind == RELKIND_PARTITIONED_TABLE)
+       {
+               ListCell *l;
+
+               foreach(l, attachrel_children)
+               {
+                       CacheInvalidateRelcacheByRelid(lfirst_oid(l));
+               }
+       }
+
        /* keep our lock until commit */
        table_close(attachrel, NoLock);
 
@@ -18150,6 +18166,25 @@ DetachPartitionFinalize(Relation rel, Relation partRel, bool concurrent,
         * included in its partition descriptor.
         */
        CacheInvalidateRelcache(rel);
+
+       /*
+        * If the partition we just detached is partitioned itself, invalidate
+        * relcache for all descendent partitions too to ensure that their
+        * rd_partcheck expression trees are rebuilt; must lock partitions
+        * before doing so, using the same lockmode as what partRel has been
+        * locked with by the caller.
+        */
+       if (partRel->rd_rel->relkind == RELKIND_PARTITIONED_TABLE)
+       {
+               List   *children;
+
+               children = find_all_inheritors(RelationGetRelid(partRel),
+                                                                          AccessExclusiveLock, NULL);
+               foreach(cell, children)
+               {
+                       CacheInvalidateRelcacheByRelid(lfirst_oid(cell));
+               }
+       }
 }
 
 /*

diff --git a/src/test/regress/expected/alter_table.out b/src/test/regress/expected/alter_table.out
index 4bee0c117358c0de0b76b78a9a7127581e343dd0..fa54bef89a5059be3201f55a9e4eafa95c23be0b 100644 (file)
--- a/src/test/regress/expected/alter_table.out
+++ b/src/test/regress/expected/alter_table.out
@@ -4489,3 +4489,23 @@ select indexrelid::regclass, indisclustered from pg_index
 (2 rows)
 
 drop table alttype_cluster;
+--
+-- Check that attaching or detaching a partitioned partition correctly leads
+-- to its partitions' constraint being updated to reflect the parent's
+-- newly added/removed constraint
+create table target_parted (a int, b int) partition by list (a);
+create table attach_parted (a int, b int) partition by list (b);
+create table attach_parted_part1 partition of attach_parted for values in (1);
+-- insert a row directly into the leaf partition so that its partition
+-- constraint is built and stored in the relcache
+insert into attach_parted_part1 values (1, 1);
+-- the following better invalidate the partition constraint of the leaf
+-- partition too...
+alter table target_parted attach partition attach_parted for values in (1);
+-- ...such that the following insert fails
+insert into attach_parted_part1 values (2, 1);
+ERROR:  new row for relation "attach_parted_part1" violates partition constraint
+DETAIL:  Failing row contains (2, 1).
+-- ...and doesn't when the partition is detached along with its own partition
+alter table target_parted detach partition attach_parted;
+insert into attach_parted_part1 values (2, 1);

diff --git a/src/test/regress/sql/alter_table.sql b/src/test/regress/sql/alter_table.sql
index dc0200adcb81fe94cd7940e662247edb0f8315fd..0c61604456c9ebd7cfb3d03214f36bca0dccf3ee 100644 (file)
--- a/src/test/regress/sql/alter_table.sql
+++ b/src/test/regress/sql/alter_table.sql
@@ -2940,3 +2940,22 @@ select indexrelid::regclass, indisclustered from pg_index
   where indrelid = 'alttype_cluster'::regclass
   order by indexrelid::regclass::text;
 drop table alttype_cluster;
+
+--
+-- Check that attaching or detaching a partitioned partition correctly leads
+-- to its partitions' constraint being updated to reflect the parent's
+-- newly added/removed constraint
+create table target_parted (a int, b int) partition by list (a);
+create table attach_parted (a int, b int) partition by list (b);
+create table attach_parted_part1 partition of attach_parted for values in (1);
+-- insert a row directly into the leaf partition so that its partition
+-- constraint is built and stored in the relcache
+insert into attach_parted_part1 values (1, 1);
+-- the following better invalidate the partition constraint of the leaf
+-- partition too...
+alter table target_parted attach partition attach_parted for values in (1);
+-- ...such that the following insert fails
+insert into attach_parted_part1 values (2, 1);
+-- ...and doesn't when the partition is detached along with its own partition
+alter table target_parted detach partition attach_parted;
+insert into attach_parted_part1 values (2, 1);