| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Unlogged materialized views |
| Date: | 2026-08-10 19:12:47 |
| Message-ID: | CAMjNa7fN6E4FwcFZpkDSr=XFD5o0y=rU68sZhYZbae7cz-3eFQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan Gonzalez V. | 2026-08-10 19:27:51 | Introduce psystem() to replace system() |
| Previous Message | Adam Brusselback | 2026-08-10 18:28:47 | Re: Avoid calling SetMatViewPopulatedState if possible |