| 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-15 01:23:36 |
| Message-ID: | E1oCA3M-000F7P-4e@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
This is a backpatch of 4e2e8d71f, applied through version 14
Branch
------
REL_14_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/2ebb8416cc4c1b8f73481335c2c6ce07286bc938
Modified Files
--------------
doc/src/sgml/ref/pg_dump.sgml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2022-07-15 03:27:02 | pgsql: Fix inconsistent parameter names between prototype and declarati |
| Previous Message | John Naylor | 2022-07-15 01:23:28 | pgsql: Clarify that pg_dump takes ACCESS SHARE lock |