diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2020-10-14 10:58:38 +0300 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2020-10-14 10:58:38 +0300 |
| commit | 178f2d560dde05b356ab2f586b8bc62514f454aa (patch) | |
| tree | 4d327c3826c6a27366554147ca70ba698f212757 /src/backend/executor/nodeModifyTable.c | |
| parent | 39b4a951003a6545268e141272e123929d0d710f (diff) | |
| download | postgresql-178f2d560dde05b356ab2f586b8bc62514f454aa.tar.gz postgresql-178f2d560dde05b356ab2f586b8bc62514f454aa.zip | |
Include result relation info in direct modify ForeignScan nodes.
FDWs that can perform an UPDATE/DELETE remotely using the "direct modify"
set of APIs need to access the ResultRelInfo of the target table. That's
currently available in EState.es_result_relation_info, but the next
commit will remove that field.
This commit adds a new resultRelation field in ForeignScan, to store the
target relation's RT index, and the corresponding ResultRelInfo in
ForeignScanState. The FDW's PlanDirectModify callback is expected to set
'resultRelation' along with 'operation'. The core code doesn't need them
for anything, they are for the convenience of FDW's Begin- and
IterateDirectModify callbacks.
Authors: Amit Langote, Etsuro Fujita
Discussion: https://www.postgresql.org/message-id/CA%2BHiwqGEmiib8FLiHMhKB%2BCH5dRgHSLc5N5wnvc4kym%2BZYpQEQ%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions