Re: Unlogged materialized views

From: Dharin Shah <dharinshah95(at)gmail(dot)com>
To: Adam Brusselback <adambrusselback(at)gmail(dot)com>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Unlogged materialized views
Date: 2026-08-11 07:46:32
Message-ID: CAOj6k6dPOyqRW+eZ1Jo7F+6Eyx2keqwGWTK6vehuKYG5-dhEWw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hey Zsolt,

+1

Will take a look at the patch

Thanks,
Dharin

On Mon, Aug 10, 2026 at 9:13 PM Adam Brusselback <adambrusselback(at)gmail(dot)com>
wrote:

> Hi Zsolt,
>
> > I like to bring up supporting unlogged materialized views again.
>
> +1 from me. Most of the MVs I've built over the years were:
> denormalized lookup tables behind a search screen, pre-aggregated
> rollups for reporting, cached joins that were too slow to run per
> request.
> Losing some of those to a crash would have been fine as refresh
> time for them wasn't a huge issue upon recovery.
>
> > * automatically refreshing unlogged views after crash recovery in a
> > background worker
>
> Something still has to notice and rebuild, and right now that would be on
> every user to write themselves. It would be nice to have this built-in IMO.
>
>
> Thanks,
> Adam
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2026-08-11 07:58:03 Re: Fix detection of truncated zstd-compressed backups
Previous Message Peter Eisentraut 2026-08-11 07:43:44 Re: Make printTableAddCell/printTableAddHeader string argument const