From: Tom Lane <tgl@sss.pgh.pa.us>
To: Hellen Jiang <hjiang@federatedwireless.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Materialized view refreshing problem
Date: Thu, 24 Aug 2023 15:02:29 -0400
Message-ID: <3961855.1692903749@sss.pgh.pa.us> (raw)
In-Reply-To: <BLAPR17MB4193164502E8A94C0A2A7080D21DA@BLAPR17MB4193.namprd17.prod.outlook.com>
References: <BLAPR17MB4193164502E8A94C0A2A7080D21DA@BLAPR17MB4193.namprd17.prod.outlook.com>
Hellen Jiang <hjiang@federatedwireless.com> writes:
> But from time and time, we found that it took forever to refresh materialized view( normally or concurrently), and there is no response to query from this materialized view.
That sounds like a locking problem. Have you looked into pg_locks
while this is happening, to see what may be waiting on what?
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, hjiang@federatedwireless.com
Subject: Re: Materialized view refreshing problem
In-Reply-To: <3961855.1692903749@sss.pgh.pa.us>
References: <BLAPR17MB4193164502E8A94C0A2A7080D21DA@BLAPR17MB4193.namprd17.prod.outlook.com> <3961855.1692903749@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox