<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Refresh Materialized View on Postgres Scripts</title><link>https://www.postgresscripts.com/tags/refresh-materialized-view/</link><description>Recent content in Refresh Materialized View on Postgres Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>PostgresScripts.com</copyright><lastBuildDate>Mon, 03 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.postgresscripts.com/tags/refresh-materialized-view/index.xml" rel="self" type="application/rss+xml"/><item><title>List PostgreSQL Materialized Views with pg_matviews</title><link>https://www.postgresscripts.com/post/list-postgresql-materialized-views-pg-matviews/</link><pubDate>Mon, 03 Aug 2026 00:00:00 +0000</pubDate><guid>https://www.postgresscripts.com/post/list-postgresql-materialized-views-pg-matviews/</guid><description>
&lt;h2 id="list-postgresql-materialized-views-with-pg_matviews"&gt;List PostgreSQL Materialized Views with pg_matviews&lt;/h2&gt;
&lt;p&gt;A materialized view carries no built-in warning label for staleness. Nothing about the row itself changes when the underlying tables mutate underneath it — a sales dashboard or a cached report join keeps returning last week's numbers with the same confidence as this morning's, and a plain &lt;code&gt;SELECT * FROM&lt;/code&gt; the view never flags the difference. &lt;a href="https://www.postgresql.org/docs/current/view-pg-matviews.html"&gt;pg_matviews&lt;/a&gt; is where that gap gets closed: a system view that lists every materialized view in the current database with its population state, index coverage, and defining query, one row per view.&lt;/p&gt;</description></item></channel></rss>