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
