From 356dd2ce5b7b0f3ea11e016f73b1f173604b8452 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 9 Aug 2022 20:37:53 -0400
Subject: [PATCH] doc: mention that COPY MATCH requires columns _in_ _order_

Question asked at SCaLE conference.

Reported-by: doc suggestion by Stephen Frost

Backpatch-through: 15
---
 doc/src/sgml/ref/copy.sgml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml
index 8aae711b3b9..63afa0d97e0 100644
--- a/doc/src/sgml/ref/copy.sgml
+++ b/doc/src/sgml/ref/copy.sgml
@@ -280,7 +280,7 @@ COPY { <replaceable class="parameter">table_name</replaceable> [ ( <replaceable
       option is set to <literal>true</literal> (or equivalent Boolean value).
       If this option is set to <literal>MATCH</literal>, the number and names
       of the columns in the header line must match the actual column names of
-      the table, otherwise an error is raised.
+      the table, in order;  otherwise an error is raised.
       This option is not allowed when using <literal>binary</literal> format.
       The <literal>MATCH</literal> option is only valid for <command>COPY
       FROM</command> commands.