| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Dull Bananas" <dull(dot)bananas0(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: DROP TRIGGER lock |
| Date: | 2024-06-08 02:53:40 |
| Message-ID: | c2a0eb3a-187b-4feb-b332-4fb186f55f49@app.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-06-09 13:31:56 | Re: CLUSTER details |
| Previous Message | Bernd Eckenfels | 2024-06-08 02:43:39 | Re: CLUSTER details |