Re: Locks under the hood on re-mat and dropping triggers
От
Laurenz Albe
Тема
Re: Locks under the hood on re-mat and dropping triggers
Дата
Msg-id
344acccba555f6a080e5937d7c6bb7af482d8f75.camel@cybertec.at
Ответ на
Locks under the hood on re-mat and dropping triggers (Wells Oliver)
Список
Дерево обсуждения
Locks under the hood on re-mat and dropping triggers Wells Oliver <wells.oliver@gmail.com>
Re: Locks under the hood on re-mat and dropping triggers Laurenz Albe <laurenz.albe@cybertec.at>
Re: Locks under the hood on re-mat and dropping triggers Wells Oliver <wells.oliver@gmail.com>
Re: Locks under the hood on re-mat and dropping triggers Tom Lane <tgl@sss.pgh.pa.us>
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 по дате отправления
