pgsql: Use ResultRelInfo ** rather than ResultRelInfo * for tuple routi

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use ResultRelInfo ** rather than ResultRelInfo * for tuple routi
Date: 2017-10-12 20:51:01
Message-ID: E1e2kRZ-00015n-VL@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Use ResultRelInfo ** rather than ResultRelInfo * for tuple routing.

The previous convention doesn't lend itself to creating ResultRelInfos
lazily, as we already do in ExecGetTriggerResultRel. This patch
doesn't make anything lazier than before, but the pending patch for
UPDATE tuple routing proposes to do so (and there might be other
opportunities as well).

Amit Khandekar with some adjustments by me.

Discussion: http://postgr.es/m/CA+TgmoYPVP9Lyf6vUFA5DwxS4c--x6LOj2y36BsJaYtp62eXPQ@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/60f7c0abef0327648c02795312d1679c66586fbb

Modified Files
--------------
src/backend/commands/copy.c | 10 ++---
src/backend/executor/execMain.c | 13 +++---
src/backend/executor/nodeModifyTable.c | 74 ++++++++++++++++++++--------------
src/include/executor/executor.h | 2 +-
src/include/nodes/execnodes.h | 2 +-
5 files changed, 57 insertions(+), 44 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2017-10-12 21:16:31 pgsql: Avoid coercing a whole-row variable that is already coerced.
Previous Message Tom Lane 2017-10-12 19:20:38 pgsql: Fix AggGetAggref() so it won't lie to aggregate final functions.