pgsql: Clarify that pg_dump takes ACCESS SHARE lock

From: John Naylor <john(dot)naylor(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Clarify that pg_dump takes ACCESS SHARE lock
Date: 2022-07-01 04:43:26
Message-ID: E1o78V2-000ctG-QG@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(at)gmail(dot)com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/4e2e8d71fe25e43fc82351bd350a6e80beee50be

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

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2022-07-01 05:22:03 pgsql: doc: Add index entry for MERGE SQL command.
Previous Message Thomas Munro 2022-07-01 02:28:42 pgsql: Harden dsm_impl.c against unexpected EEXIST.