Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJhSu-006Iu8-1G for pgsql-admin@arkaria.postgresql.org; Tue, 18 Jun 2024 22:38:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sJhSr-004q2N-Ac for pgsql-admin@arkaria.postgresql.org; Tue, 18 Jun 2024 22:38:10 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJhSq-004q1e-Ug for pgsql-admin@lists.postgresql.org; Tue, 18 Jun 2024 22:38:09 +0000 Received: from chi208.greengeeks.net ([65.60.38.74]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sJhSp-001z6s-0t for pgsql-admin@postgresql.org; Tue, 18 Jun 2024 22:38:08 +0000 Received: from [217.180.196.83] (port=60812 helo=Incisivetech) by chi208.greengeeks.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.97.1) (envelope-from ) id 1sJhSt-00000001R5h-1ch1; Tue, 18 Jun 2024 22:38:05 +0000 From: To: "'Wells Oliver'" , "'pgsql-admin'" References: In-Reply-To: Subject: RE: Materialized views & dead tuples Date: Tue, 18 Jun 2024 18:38:03 -0400 Message-ID: <004d01dac1d0$2ee1a8b0$8ca4fa10$@incisivetechgroup.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004E_01DAC1AE.A7D02FC0" X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHE7C9l2oOpIuCcEL4hgyaFhiKDVLH5x3Sw Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - chi208.greengeeks.net X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - incisivetechgroup.com X-Get-Message-Sender-Via: chi208.greengeeks.net: authenticated_id: lennam@incisivetechgroup.com X-Authenticated-Sender: chi208.greengeeks.net: lennam@incisivetechgroup.com X-Source: X-Source-Args: X-Source-Dir: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multipart message in MIME format. ------=_NextPart_000_004E_01DAC1AE.A7D02FC0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Get materialized views details=20 =20 Select shcmename,matviewname,matviewowner from pg_matviews;=20 =20 --Raju=20 =20 From: Wells Oliver =20 Sent: Tuesday, June 18, 2024 6:29 PM To: pgsql-admin Subject: Materialized views & dead tuples =20 Apologies for the daft question, but I am surprised to see materialized = views show up in pg_stat_user_tables with lots of dead tuples. These are = rematerialized nightly and, I thought, this had the effect of = replacing/recreating them anew. Can someone shed some light on this? =20 --=20 Wells Oliver wells.oliver@gmail.com =20 ------=_NextPart_000_004E_01DAC1AE.A7D02FC0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable

Get materialized views details =

 

Select shcmename,matviewname,matviewowner from = pg_matviews;

 

--Raju

 

From: Wells Oliver = <wells.oliver@gmail.com>
Sent: Tuesday, June 18, 2024 = 6:29 PM
To: pgsql-admin = <pgsql-admin@postgresql.org>
Subject: Materialized views = & dead tuples

 

Apologies for the = daft question, but I am surprised to see materialized views = show up in pg_stat_user_tables with lots of dead tuples. These are = rematerialized nightly and, I thought, this had the effect of = replacing/recreating them anew. Can someone shed some light on = this?

 

--

------=_NextPart_000_004E_01DAC1AE.A7D02FC0--