From 60f7c0abef0327648c02795312d1679c66586fbb Mon Sep 17 00:00:00 2001
From: Robert Haas
Date: Thu, 12 Oct 2017 16:50:53 -0400
Subject: 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
---
 src/include/executor/executor.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/include/executor/executor.h')

diff --git a/src/include/executor/executor.h b/src/include/executor/executor.h
index 37fd6b2700a..c4ecf0d50f3 100644
--- a/src/include/executor/executor.h
+++ b/src/include/executor/executor.h
@@ -210,7 +210,7 @@ extern void ExecSetupPartitionTupleRouting(Relation rel,
 							   Index resultRTindex,
 							   EState *estate,
 							   PartitionDispatch **pd,
-							   ResultRelInfo **partitions,
+							   ResultRelInfo ***partitions,
 							   TupleConversionMap ***tup_conv_maps,
 							   TupleTableSlot **partition_tuple_slot,
 							   int *num_parted, int *num_partitions);
-- 
cgit v1.2.3