aboutsummaryrefslogtreecommitdiff
path: root/src/backend/jit/llvm/llvmjit_inline.cpp
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2020-05-16 18:16:31 +0900
committerMichael Paquier <michael@paquier.xyz>2020-05-16 18:16:31 +0900
commitb4ded2f227f3ec1144a4691d2326eb90174447db (patch)
tree94c6588a9e9f7f6773c98c42203b19deb24935af /src/backend/jit/llvm/llvmjit_inline.cpp
parentc8b1c953b8be8ede059b104198c5603a251eb19f (diff)
downloadpostgresql-b4ded2f227f3ec1144a4691d2326eb90174447db.tar.gz
postgresql-b4ded2f227f3ec1144a4691d2326eb90174447db.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