From: Laurenz Albe <laurenz.albe@cybertec.at>
To: nikolai.berkoff <nikolai.berkoff@pm.me>
To: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: COMMENT ON lock
Date: Tue, 18 Jan 2022 15:37:35 +0100
Message-ID: <faffeca61e7bb1338a7da72dc880bd47624adc3d.camel@cybertec.at> (raw)
In-Reply-To: <_0HDHIGcCdCsUyXn22QwI2FEuNR6Fs71rtgGX6hfyBlUh5rrnE2qMmvIFu9EY4Pijr2gUmJEAXCjuNU2Oxku9TryLp9CdHllpsCfN3gD0-Y=@pm.me>
References: <_0HDHIGcCdCsUyXn22QwI2FEuNR6Fs71rtgGX6hfyBlUh5rrnE2qMmvIFu9EY4Pijr2gUmJEAXCjuNU2Oxku9TryLp9CdHllpsCfN3gD0-Y=@pm.me>
On Tue, 2022-01-18 at 14:11 +0000, nikolai.berkoff wrote:
> I wanted to know what lock the COMMENT ON command took and I had to look in the
> source code, makes sense to me that it should be documented. I've also added
> it to the list of commands that take a SHARE UPDATE EXCLUSIVE lock.
+1, but SHARE ACCESS EXCLUSIVE should be marked up with <literal>.
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, nikolai.berkoff@pm.me, pgsql-docs@lists.postgresql.org
Subject: Re: COMMENT ON lock
In-Reply-To: <faffeca61e7bb1338a7da72dc880bd47624adc3d.camel@cybertec.at>
* 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