From 0d46771eaaf77ad08555cf34e421234d5943edfa Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 7 Apr 2021 12:21:54 -0400 Subject: [PATCH] Comment cleanup for a1115fa07. Amit Langote Discussion: https://postgr.es/m/CA+HiwqEcawatEaUh1uTbZMEZTJeLzbroRTz9_X9Z5CFjTWJkhw@mail.gmail.com --- src/backend/executor/nodeModifyTable.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/src/backend/executor/nodeModifyTable.c b/src/backend/executor/nodeModifyTable.c index 6a16752c73..c5a2a9a054 100644 --- a/src/backend/executor/nodeModifyTable.c +++ b/src/backend/executor/nodeModifyTable.c @@ -377,9 +377,6 @@ ExecComputeStoredGenerated(ResultRelInfo *resultRelInfo, * * INSERT queries may need a projection to filter out junk attrs in the tlist. * - * This is "one-time" for any given result rel, but we might touch - * more than one result rel in the course of a partitioned INSERT. - * * This is also a convenient place to verify that the * output of an INSERT matches the target table. */ @@ -447,7 +444,7 @@ ExecInitInsertProjection(ModifyTableState *mtstate, * identity info in the junk attrs. * * This is "one-time" for any given result rel, but we might touch more than - * one result rel in the course of a partitioned UPDATE, and each one needs + * one result rel in the course of an inherited UPDATE, and each one needs * its own projection due to possible column order variation. * * This is also a convenient place to verify that the output of an UPDATE