Re: COMMENT ON lock

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: "nikolai(dot)berkoff" <nikolai(dot)berkoff(at)pm(dot)me>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: COMMENT ON lock
Date: 2022-01-18 14:37:35
Message-ID: faffeca61e7bb1338a7da72dc880bd47624adc3d.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Eric Mutta 2022-01-18 23:00:18 Re: Typo in "27.2.8. Synchronous Replication"
Previous Message nikolai.berkoff 2022-01-18 14:11:52 COMMENT ON lock