]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Prevent duplicate RTEPermissionInfo for plain-inheritance parents
authorAmit Langote <amitlan@postgresql.org>
Thu, 26 Oct 2023 02:53:41 +0000 (11:53 +0900)
committerAmit Langote <amitlan@postgresql.org>
Thu, 26 Oct 2023 02:53:41 +0000 (11:53 +0900)
commit178ee1d858d89f6d86f42a84bd4b8014ddfa7245
tree0293a526187a63ecad4de1451c4a104fc317e712
parentd76606f077c3bd1c0fc161fd4dd8666b2d997164
Prevent duplicate RTEPermissionInfo for plain-inheritance parents

Currently, expand_single_inheritance_child() doesn't reset
perminfoindex in a plain-inheritance parent's child RTE, because
prior to 387f9ed0a0, the executor would use the first child RTE to
locate the parent's RTEPermissionInfo.  That in turn causes
add_rte_to_flat_rtable() to create an extra RTEPermissionInfo
belonging to the parent's child RTE with the same content as the one
belonging to the parent's original ("root") RTE.

In 387f9ed0a0, we changed things so that the executor can now use the
parent's "root" RTE for locating its RTEPermissionInfo instead of the
child RTE, so the latter's perminfoindex need not be set anymore, so
make it so.

Reported-by: Tom Lane
Discussion: https://postgr.es/m/839708.1698174464@sss.pgh.pa.us
Backpatch-through: 16
src/backend/optimizer/util/inherit.c