Re: Unlogged materialized views

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
Cc: Adam Brusselback <adambrusselback(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Unlogged materialized views
Date: 2026-09-24 17:35:09
Message-ID: CAN4CZFOLPsqmDoyU_BX8==Qx4_cvF5c4CZb-K3aUn2OESdDCjw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you for the feedback and suggestions!

I rebased again; the patch no longer increments the
controlfile/catalog version to make conflicts less likely.

I included the changes from 0004, and added a few other minor changes/fixes.

I also found another issue while testing replication scenarios. To fix
that, the counter is now based on the LSN, not the timeline, this is
the most significant change compared to v3.

Another open question I want to point out is that I found a pg_dump
failure with --no-unlogged-table-data. For now I chose the option
where this flag doesn't affect materialized views, as they are not
tables, but I am not sure if this is the proper solution.

Attachment Content-Type Size
v4-0002-Replace-pg_class.relispopulated-with-epoch-capabl.patch application/octet-stream 25.0 KB
v4-0001-Add-durable-unlogged-reset-LSN-to-pg_control.patch application/octet-stream 8.6 KB
v4-0003-Add-unlogged-materialized-views.patch application/octet-stream 50.5 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-09-24 17:41:48 Re: Add REPACK progress phases for logical decoding setup
Previous Message Bernd Reiß 2026-09-24 17:33:59 Re: [Patch] New pg_stat_tablespace view