Simplify and encapsulate tuple routing support code.
authorRobert Haas <rhaas@postgresql.org>
Thu, 4 Jan 2018 20:48:15 +0000 (15:48 -0500)
committerRobert Haas <rhaas@postgresql.org>
Thu, 4 Jan 2018 20:48:15 +0000 (15:48 -0500)
commitcc6337d2fed598d4b5ac54d9a62708182b83a81e
treef83d3b74ecfb5884f158b45766708c1aa2e5f4ae
parentd3fb72ea6de58d285e278459bca9d7cdf7f6a38b
Simplify and encapsulate tuple routing support code.

Instead of having ExecSetupPartitionTupleRouting return multiple out
parameters, have it return a pointer to a structure containing all of
those different things.  Also, provide and use a cleanup function,
ExecCleanupTupleRouting, instead of cleaning up all of the resources
allocated by ExecSetupPartitionTupleRouting individually.

Amit Khandekar, reviewed by Amit Langote, David Rowley, and me

Discussion: http://postgr.es/m/CAJ3gD9fWfxgKC+PfJZF3hkgAcNOy-LpfPxVYitDEXKHjeieWQQ@mail.gmail.com
src/backend/commands/copy.c
src/backend/executor/execPartition.c
src/backend/executor/nodeModifyTable.c
src/include/executor/execPartition.h
src/include/nodes/execnodes.h