Re: Locks under the hood on re-mat and dropping triggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wells Oliver <wells(dot)oliver(at)gmail(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Locks under the hood on re-mat and dropping triggers
Date: 2022-05-20 20:41:14
Message-ID: 489128.1653079274@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Wells Oliver <wells(dot)oliver(at)gmail(dot)com> writes:
> 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.

You'd need to show a test case. Personally I'm wondering if there's a
foreign key constraint connecting the troublesome table to some table
used by the matview.

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message aditya desai 2022-05-21 03:25:40 Re: Steps to Install archived Postgres 9.3 and 9.6
Previous Message Ron 2022-05-20 19:57:47 Re: Many databases ou many schemas