aboutsummaryrefslogtreecommitdiff
path: root/contrib/postgres_fdw
diff options
context:
space:
mode:
authorAndrew Dunstan <andrew@dunslane.net>2018-06-30 12:25:49 -0400
committerAndrew Dunstan <andrew@dunslane.net>2018-06-30 12:25:49 -0400
commit1e9c8580904625576871eeb2efec7f04d4c3bc1c (patch)
tree6093afd9440b732c2b4f2c040b7a3e83b6f163ae /contrib/postgres_fdw
parent2c64d200484c40c1bfbd532bf140bea672f267a1 (diff)
downloadpostgresql-1e9c8580904625576871eeb2efec7f04d4c3bc1c.tar.gz
postgresql-1e9c8580904625576871eeb2efec7f04d4c3bc1c.zip
pgindent run prior to branching
Diffstat (limited to 'contrib/postgres_fdw')
-rw-r--r--contrib/postgres_fdw/postgres_fdw.c19
1 files changed, 9 insertions, 10 deletions
diff --git a/contrib/postgres_fdw/postgres_fdw.c b/contrib/postgres_fdw/postgres_fdw.c
index 78b0f43ca83..9369cfc2656 100644
--- a/contrib/postgres_fdw/postgres_fdw.c
+++ b/contrib/postgres_fdw/postgres_fdw.c
@@ -2020,12 +2020,11 @@ postgresBeginForeignInsert(ModifyTableState *mtstate,
/*
* If the foreign table is a partition, we need to create a new RTE
* describing the foreign table for use by deparseInsertSql and
- * create_foreign_modify() below, after first copying the parent's
- * RTE and modifying some fields to describe the foreign partition to
- * work on. However, if this is invoked by UPDATE, the existing RTE
- * may already correspond to this partition if it is one of the
- * UPDATE subplan target rels; in that case, we can just use the
- * existing RTE as-is.
+ * create_foreign_modify() below, after first copying the parent's RTE and
+ * modifying some fields to describe the foreign partition to work on.
+ * However, if this is invoked by UPDATE, the existing RTE may already
+ * correspond to this partition if it is one of the UPDATE subplan target
+ * rels; in that case, we can just use the existing RTE as-is.
*/
rte = list_nth(estate->es_range_table, resultRelation - 1);
if (rte->relid != RelationGetRelid(rel))
@@ -2035,10 +2034,10 @@ postgresBeginForeignInsert(ModifyTableState *mtstate,
rte->relkind = RELKIND_FOREIGN_TABLE;
/*
- * For UPDATE, we must use the RT index of the first subplan
- * target rel's RTE, because the core code would have built
- * expressions for the partition, such as RETURNING, using that
- * RT index as varno of Vars contained in those expressions.
+ * For UPDATE, we must use the RT index of the first subplan target
+ * rel's RTE, because the core code would have built expressions for
+ * the partition, such as RETURNING, using that RT index as varno of
+ * Vars contained in those expressions.
*/
if (plan && plan->operation == CMD_UPDATE &&
resultRelation == plan->nominalRelation)