diff options
author | Michael Paquier <michael@paquier.xyz> | 2020-05-16 18:16:37 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2020-05-16 18:16:37 +0900 |
commit | 70ae82b9b4b5871604ba4e98ebe0f32bef223200 (patch) | |
tree | 2b4364a460db6d597ce8aa9ccaaf53700e66206d /src/backend/jit/llvm/llvmjit_inline.cpp | |
parent | ee39a4b9e475348dd3de82781a54be82e63a3186 (diff) | |
download | postgresql-70ae82b9b4b5871604ba4e98ebe0f32bef223200.tar.gz postgresql-70ae82b9b4b5871604ba4e98ebe0f32bef223200.zip |
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
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_inline.cpp')
0 files changed, 0 insertions, 0 deletions