From: Nathan Bossart <nathandbossart@gmail.com>
To: Florin Irion <irionr@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: pg_dump shared locks documentation
Date: Wed, 30 Mar 2022 15:19:29 -0700
Message-ID: <20220330221929.GA47505@nathanxps13> (raw)
In-Reply-To: <f84cbf9e-cf4b-a9eb-9667-5fadd913d5ca@gmail.com>
References: <202203151506.55cjea5lmp2l@alvherre.pgsql>
<324244.1647359709@sss.pgh.pa.us>
<f84cbf9e-cf4b-a9eb-9667-5fadd913d5ca@gmail.com>
On Tue, Mar 15, 2022 at 11:21:41PM +0100, Florin Irion wrote:
> So, I made the link to ACCESS SHARE, pointing to section 13.3.1. "Table-Level Locks" , was this what you had in mind?
>
> V2 attached.
LGTM. I've marked the commitfest entry as ready-for-committer.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: nathandbossart@gmail.com, irionr@gmail.com, tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, pgsql-docs@lists.postgresql.org
Subject: Re: pg_dump shared locks documentation
In-Reply-To: <20220330221929.GA47505@nathanxps13>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox