You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
A future commit will move the checkAsUser field from RangeTblEntryto a new node that, unlike RTEs, will only be created for tablesmentioned in the query but not for the inheritance child relationsadded to the query by the planner. So, checkAsUser value for agiven child relation will have to be obtained by referring to thatfor its ancestor mentioned in the query.In preparation, it seems better to expand the use of RelOptInfo.useridduring planning in place of rte->checkAsUser so that there will befewer places to adjust for the above change.Given that the child-to-ancestor mapping is not available during theexecution of a given "child" ForeignScan node, add a checkAsUserfield 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