aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEtsuro Fujita <efujita@postgresql.org>2022-09-22 15:55:06 +0900
committerEtsuro Fujita <efujita@postgresql.org>2022-09-22 15:55:06 +0900
commit6359e4b0fe7138f7b89e07858e1563c46d36459a (patch)
treec153bc42efb72a79985bf4650a8438eeebe1a28c
parente2744369db871bb6e998ea10fe1d7cdf68f57062 (diff)
downloadpostgresql-6359e4b0fe7138f7b89e07858e1563c46d36459a.tar.gz
postgresql-6359e4b0fe7138f7b89e07858e1563c46d36459a.zip
Fix thinko in comment.
This comment has been wrong since its introduction in commit 0d5f05cde; backpatch to v12 where that came in. Discussion: https://postgr.es/m/CAPmGK14VGf-xQjGQN4o1QyAbXAaxugU5%3DqfcmTDh1iufUDnV_w%40mail.gmail.com
-rw-r--r--src/backend/commands/copy.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/backend/commands/copy.c b/src/backend/commands/copy.c
index 12ce8c77791..1588e733e01 100644
--- a/src/backend/commands/copy.c
+++ b/src/backend/commands/copy.c
@@ -2918,8 +2918,8 @@ CopyFrom(CopyState cstate)
* For partitioned tables we can't support multi-inserts when there
* are any statement level insert triggers. It might be possible to
* allow partitioned tables with such triggers in the future, but for
- * now, CopyMultiInsertInfoFlush expects that any before row insert
- * and statement level insert triggers are on the same relation.
+ * now, CopyMultiInsertInfoFlush expects that any after row insert and
+ * statement level insert triggers are on the same relation.
*/
insertMethod = CIM_SINGLE;
}