diff options
| author | Alvaro Herrera | 2022-11-30 11:07:03 +0000 |
|---|---|---|
| committer | Alvaro Herrera | 2022-11-30 11:07:03 +0000 |
| commit | 599b33b9492dfefd1219c1d31801f40b3ba90b0d (patch) | |
| tree | 37e6681f524f31d78072cdf7498d869993b94030 /contrib/jsonb_plpython | |
| parent | d2a4490401f2ddc878134a1fd75ef4482e403e47 (diff) | |
Stop accessing checkAsUser via RTE in some cases
A future commit will move the checkAsUser field from RangeTblEntry
to a new node that, unlike RTEs, will only be created for tables
mentioned in the query but not for the inheritance child relations
added to the query by the planner. So, checkAsUser value for a
given child relation will have to be obtained by referring to that
for its ancestor mentioned in the query.
In preparation, it seems better to expand the use of RelOptInfo.userid
during planning in place of rte->checkAsUser so that there will be
fewer places to adjust for the above change.
Given that the child-to-ancestor mapping is not available during the
execution of a given "child" ForeignScan node, add a checkAsUser
field to ForeignScan to carry the child relation's RelOptInfo.userid.
Author: Amit Langote <amitlangote09@gmail.com>
Discussion: https://postgr.es/m/CA+HiwqGFCs2uq7VRKi7g+FFKbP6Ea_2_HkgZb2HPhUfaAKT3ng@mail.gmail.com
Diffstat (limited to 'contrib/jsonb_plpython')
0 files changed, 0 insertions, 0 deletions