Postgres Pro
Downloads
Home   >   mailing lists

Re: Locks under the hood on re-mat and dropping triggers - Mailing list pgsql-admin

From Wells Oliver
Subject Re: Locks under the hood on re-mat and dropping triggers
Date
Msg-id CAOC+FBUP248PG-n_w3i4z6FcLuf=X-KDkZ-F1F2OPnDgFbZDwQ@mail.gmail.com
Whole thread Raw
In response to Re: Locks under the hood on re-mat and dropping triggers  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Locks under the hood on re-mat and dropping triggers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
Tree view
but what I am seeing is this lock even when the trigger and table are not at all used by an entirely separate mat-view being re-materialized.

On Fri, May 20, 2022 at 12:12 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Thu, 2022-05-19 at 14:37 -0700, Wells Oliver wrote:
> Dropping triggers from some table yields a lock while a concurrent refresh of a materialized
> view in another schema entirely is running-- why is this?

That is because dropping a trigger requires a (brief) ACCESS EXCLUSIVE lock on the table,
which conflicts with all concurrent access to the table.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com


--

pgsql-admin by date:

Previous
From: aditya desai
Date:
Subject: Steps to Install archived Postgres 9.3 and 9.6
Next
From: Ron
Date:
Subject: Re: Many databases ou many schemas