aboutsummaryrefslogtreecommitdiff
path: root/src/common
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2022-06-21 07:52:41 +0530
committerAmit Kapila <akapila@postgresql.org>2022-06-21 08:03:30 +0530
commit52d5ea9adb010d0908e8962842571cd1f6c2d66c (patch)
tree4ad10244f26736df90d386db8f1d9bf74d8effbb /src/common
parent0980adfd4d021e3329bf41452ce1a1210321974f (diff)
downloadpostgresql-52d5ea9adb010d0908e8962842571cd1f6c2d66c.tar.gz
postgresql-52d5ea9adb010d0908e8962842571cd1f6c2d66c.zip
Fix partition table's REPLICA IDENTITY checking on the subscriber.
In logical replication, we will check if the target table on the subscriber is updatable by comparing the replica identity of the table on the publisher with the table on the subscriber. When the target table is a partitioned table, we only check its replica identity but not for the partition tables. This leads to assertion failure while applying changes for update/delete as we expect those to succeed only when the corresponding partition table has a primary key or has a replica identity defined. Fix it by checking the replica identity of the partition table while applying changes. Reported-by: Shi Yu Author: Shi Yu, Hou Zhijie Reviewed-by: Amit Langote, Amit Kapila Backpatch-through: 13, where it was introduced Discussion: https://postgr.es/m/OSZPR01MB6310F46CD425A967E4AEF736FDA49@OSZPR01MB6310.jpnprd01.prod.outlook.com
Diffstat (limited to 'src/common')
0 files changed, 0 insertions, 0 deletions