pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Euler Taveira <euler@eulerto.com>
To: Dull Bananas <dull.bananas0@gmail.com>
To: pgsql-docs@lists.postgresql.org
Subject: Re: DROP TRIGGER lock
Date: Fri, 07 Jun 2024 23:53:40 -0300
Message-ID: <c2a0eb3a-187b-4feb-b332-4fb186f55f49@app.fastmail.com> (raw)
In-Reply-To: <CAKmgnAiZB3o0Ki9fCQXM00vt+e0hYUXqhQVaRsiHOhTUAVO52w@mail.gmail.com>
References: <CAKmgnAiZB3o0Ki9fCQXM00vt+e0hYUXqhQVaRsiHOhTUAVO52w@mail.gmail.com>

On Fri, Jun 7, 2024, at 12:06 PM, Dull Bananas wrote:
> On these pages, it should be mentioned that DROP TRIGGER acquires an ACCESS EXCLUSIVE lock:
> 
 <https://www.postgresql.org/docs/current/explicit-locking.html;
> https://www.postgresql.org/docs/16/explicit-locking.html#LOCKING-TABLES
> 
> https://www.postgresql.org/docs/16/sql-droptrigger.html <https://www.postgresql.org/docs/current/sql-droptrigger.html;

If I would add such information it would be in the latter. AFAICS the former
provides some examples of SQL commands that take AccessExclusiveLock. If you
search for AccessExclusiveLock into src/backend/commands/* you will notice that
there are more commands that were not mentioned in the Table-Level Locks
section.

Feel free to propose a patch.


--
Euler Taveira
EDB   https://www.enterprisedb.com/

view thread (2+ messages)

Message-ID: <c2a0eb3a-187b-4feb-b332-4fb186f55f49@app.fastmail.com>
Permalink:  ../c2a0eb3a-187b-4feb-b332-4fb186f55f49@app.fastmail.com/
Also on:    postgresql.org/message-id/c2a0eb3a-187b-4feb-b332-4fb186f55f49@app.fastmail.com

 · 

reply
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: euler@eulerto.com, dull.bananas0@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: DROP TRIGGER lock
  In-Reply-To: <c2a0eb3a-187b-4feb-b332-4fb186f55f49@app.fastmail.com>

* 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