aboutsummaryrefslogtreecommitdiff
path: root/src/backend/jit/llvm/llvmjit_inline.cpp
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2022-10-07 19:37:48 +0200
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2022-10-07 19:37:48 +0200
commit7d520e68ea1e38a9f7ad1d04bd5f95d53eef6cd4 (patch)
tree4b1f85bda88879e16cf953537930740a6ab76b2c /src/backend/jit/llvm/llvmjit_inline.cpp
parent92941f26435ce3910bb9320fd92bda1e3dd4c6b5 (diff)
downloadpostgresql-7d520e68ea1e38a9f7ad1d04bd5f95d53eef6cd4.tar.gz
postgresql-7d520e68ea1e38a9f7ad1d04bd5f95d53eef6cd4.zip
Fix self-referencing foreign keys with partitioned tables
There are a number of bugs in this area. Two of them are fixed here, namely: 1. get_relation_idx_constraint_oid does not restrict the type of constraint that's returned, so with sufficient bad luck it can return the OID of a foreign key constraint. This has the effect that a primary key in a partition can end up as a child of a foreign key, which makes no sense (it needs to be the child of the equivalent primary key.) Change the API contract so that only index-backed constraints are returned, mimicking get_constraint_index(). 2. Both CloneFkReferenced and CloneFkReferencing clone a self-referencing foreign key, so the partition ends up with a duplicate foreign key. Change the former function to ignore such constraints. Add some tests to verify that things are better now. (However, these new tests show some additional misbehavior that will be fixed later -- namely that there's a constraint marked NOT VALID.) Backpatch to 12, where these constraints are possible at all. Author: Jehan-Guillaume de Rorthais <jgdr@dalibo.com> Discussion: https://postgr.es/m/20220603154232.1715b14c@karst
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_inline.cpp')
0 files changed, 0 insertions, 0 deletions