public inbox for [email protected]
help / color / mirror / Atom feedFrom: Wells Oliver <[email protected]>
To: Laurenz Albe <[email protected]>
Cc: pgsql-admin <[email protected]>
Subject: Re: Locks under the hood on re-mat and dropping triggers
Date: Fri, 20 May 2022 12:35:47 -0700
Message-ID: <CAOC+FBUP248PG-n_w3i4z6FcLuf=X-KDkZ-F1F2OPnDgFbZDwQ@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAOC+FBXr9mbGAS=D2wNUM7Qky9u_vQA=DXy=A4puhGrbjUFU+g@mail.gmail.com>
<[email protected]>
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 <[email protected]>
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
>
--
Wells Oliver
[email protected] <[email protected]>
view thread (4+ messages) latest in thread
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Locks under the hood on re-mat and dropping triggers
In-Reply-To: <CAOC+FBUP248PG-n_w3i4z6FcLuf=X-KDkZ-F1F2OPnDgFbZDwQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox