postgres.git / summary / log / commit / refs

commit    2ebb8416cc4c1b8f73481335c2c6ce07286bc938
Author:   John Naylor <john.naylor@postgresql.org>
Date:     Fri Jul 01 04:41:36 2022 +0000

    Clarify that pg_dump takes ACCESS SHARE lock
    
    Add link to the description of lock levels to avoid confusing "shared locks"
    with SHARE locks.
    
    Florin Irion
    
    Reviewed-by: Álvaro Herrera, Tom Lane, and Nathan Bossart
    Discussion: https://www.postgresql.org/message-id/flat/d0f30cc2-3c76-1d43-f291-7c4b2872d653@gmail.com
    
    This is a backpatch of 4e2e8d71f, applied through version 14


 doc/src/sgml/ref/pg_dump.sgml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index a6c0788592b..b6b66bf068c 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -372,8 +372,8 @@ PostgreSQL documentation
        <para>
         Requesting exclusive locks on database objects while running a parallel dump could
         cause the dump to fail. The reason is that the <application>pg_dump</application> leader process
-        requests shared locks on the objects that the worker processes are going to dump later
-        in order to
+        requests shared locks (<link linkend="locking-tables">ACCESS SHARE</link>) on the
+        objects that the worker processes are going to dump later in order to
         make sure that nobody deletes them and makes them go away while the dump is running.
         If another client then requests an exclusive lock on a table, that lock will not be
         granted but will be queued waiting for the shared lock of the leader process to be


[parent: e1d5ac3118be]