Fix assertion with relation using REPLICA IDENTITY FULL in subscriber
authorMichael Paquier <[email protected]>
Sat, 16 May 2020 09:16:41 +0000 (18:16 +0900)
committerMichael Paquier <[email protected]>
Sat, 16 May 2020 09:16:41 +0000 (18:16 +0900)
commit3acb30b49818754845b256f0f8d4c81705f047cf
tree082cc9816e93029724f4a6c78c683c3da00cd6b0
parent9d66ea5dee0091e12e0575b0798fa8ba9645e8bb
Fix assertion with relation using REPLICA IDENTITY FULL in subscriber

In a logical replication subscriber, a table using REPLICA IDENTITY FULL
which has a primary key would try to use the primary key's index
available to scan for a tuple, but an assertion only assumed as correct
the case of an index associated to REPLICA IDENTITY USING INDEX.  This
commit corrects the assertion so as the use of a primary key index is a
valid case.

Reported-by: Dilip Kumar
Analyzed-by: Dilip Kumar
Author: Euler Taveira
Reviewed-by: Michael Paquier, Masahiko Sawada
Discussion: https://postgr.es/m/CAFiTN-u64S5bUiPL1q5kwpHNd0hRnf1OE-bzxNiOs5zo84i51w@mail.gmail.com
Backpatch-through: 10
src/backend/executor/execReplication.c
src/test/subscription/t/001_rep_changes.pl