| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Jim Jones <jim(dot)jones(at)uni-muenster(dot)de> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Adam Brusselback <adambrusselback(at)gmail(dot)com> |
| Subject: | Re: Unlogged materialized views |
| Date: | 2026-10-15 22:00:16 |
| Message-ID: | CAN4CZFOrHgLMBngZE21CsfC_Mqj4vbeRdkZouUW6dNb1mu2f3Q@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I realise it is a matter of taste, but I find the generic error message
> more accurate than this new one.
I wanted to improve it, but I agree that doing it differently for
matviews might be confusing instead, so I removed that part from the
patch, now it gives the same generic recovery message.
> The hint in copy is not very accurate during a recovery session.
I handled COPY the same way your patch does for unlogged tables, with
the same generic message about recovery.
v6 contains these changes in 0003, otherwise it's a trivial rebase on
current master.
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Add-durable-unlogged-reset-LSN-to-pg_control.patch | application/octet-stream | 8.6 KB |
| v6-0003-Add-unlogged-materialized-views.patch | application/octet-stream | 49.5 KB |
| v6-0002-Replace-pg_class.relispopulated-with-epoch-capabl.patch | application/octet-stream | 25.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Baji Shaik | 2026-10-15 22:00:39 | Re: [PATCH] Doc fix for autovacuum_max_parallel_workers |
| Previous Message | Bilal Kahraman | 2026-10-15 21:52:23 | Re: index prefetching |