Minor fixes in COPY progress docs

Author: Justin Pryzby
Discussion: https://postgr.es/m/CAFp7Qwr6_FmRM6pCO0x_a0mymOfX_Gg+FEKet4XaTGSW=LitKQ@mail.gmail.com

diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index 43fe8ae383eb923bdc6a7c31ece1178ec625cf3a..3cdb1aff3c8fc0da6684184d156f2e095a6d1c53 100644 (file)
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6414,9 +6414,9 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
   
    Whenever COPY is running, the
    pg_stat_progress_copy view will contain one row
-   for each backend that is currently running COPY command.
-   The table bellow describes the information that will be reported and provide
-   information how to interpret it.
+   for each backend that is currently running a COPY command.
+   The table below describes the information that will be reported and provides
+   information about how to interpret it.
   
 
   
@@ -6445,7 +6445,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
 
      
       
-       datid text
+       datid oid
       
       
        OID of the database to which this backend is connected.
@@ -6467,7 +6467,7 @@ SELECT pg_stat_get_backend_pid(s.backendid) AS pid,
       
       
        OID of the table on which the COPY command is executed.
-       It is set to 0 if SELECT query is provided.
+       It is set to 0 if copying from a SELECT query.