aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2022-08-09 20:37:53 -0400
committerBruce Momjian <bruce@momjian.us>2022-08-09 20:37:53 -0400
commit356dd2ce5b7b0f3ea11e016f73b1f173604b8452 (patch)
tree92e15714609b828adba6220c0965589e9f117bb9
parent0b039e3a8489c08ec61b4d40382047c389af91ad (diff)
downloadpostgresql-356dd2ce5b7b0f3ea11e016f73b1f173604b8452.tar.gz
postgresql-356dd2ce5b7b0f3ea11e016f73b1f173604b8452.zip
doc: mention that COPY MATCH requires columns _in_ _order_
Question asked at SCaLE conference. Reported-by: doc suggestion by Stephen Frost Backpatch-through: 15
-rw-r--r--doc/src/sgml/ref/copy.sgml2
1 files changed, 1 insertions, 1 deletions
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.