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

From Laurenz Albe
Subject Re: Locks under the hood on re-mat and dropping triggers
Date
Msg-id 344acccba555f6a080e5937d7c6bb7af482d8f75.camel@cybertec.at
Whole thread Raw
In response to Locks under the hood on re-mat and dropping triggers  (Wells Oliver <wells.oliver@gmail.com>)
Responses Re: Locks under the hood on re-mat and dropping triggers  (Wells Oliver <wells.oliver@gmail.com>)
List pgsql-admin
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: Ron
Date:
Subject: Re: Postgres switchover and switchback
Next
From: khoff
Date:
Subject: Re: bash or sql script to copy foreign table to locale table