doc: clarify that "excluded" ON CONFLICT is a single row

Original patch by David G. Johnston.

Reported-by: David G. Johnston
Discussion: https://postgr.es/m/CAKFQuwa4J0+WuO7kW1PLbjoEvzPN+Q_j+P2bXxNnCLaszY7ZdQ@mail.gmail.com

Backpatch-through: 10

diff --git a/doc/src/sgml/ref/insert.sgml b/doc/src/sgml/ref/insert.sgml
index 558660ccc587de1e9da782f4d276f760f0158275..c3f49f7398071e4d18edb4797715d5fe2fed0d6c 100644 (file)
--- a/doc/src/sgml/ref/insert.sgml
+++ b/doc/src/sgml/ref/insert.sgml
@@ -181,7 +181,7 @@ INSERT INTO table_name [ AS 
         provided, it completely hides the actual name of the table.
         This is particularly useful when ON CONFLICT DO UPDATE
         targets a table named excluded, since that will otherwise
-        be taken as the name of the special table representing rows proposed
+        be taken as the name of the special table representing the row proposed
         for insertion.
        
       
@@ -401,7 +401,7 @@ INSERT INTO table_name [ AS 
         conflict.  The SET and
         WHERE clauses in ON CONFLICT DO
         UPDATE have access to the existing row using the
-        table's name (or an alias), and to rows proposed for insertion
+        table's name (or an alias), and to the row proposed for insertion
         using the special excluded table.
         SELECT privilege is required on any column in the
         target table where corresponding excluded