From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | smithpb2250(at)gmail(dot)com, vignesh21(at)gmail(dot)com, nathandbossart(at)gmail(dot)com, jakub(dot)wartak(at)enterprisedb(dot)com, stark(dot)cfm(at)gmail(dot)com, hlinnaka(at)iki(dot)fi, barwick(at)gmail(dot)com, jchampion(at)timescale(dot)com, pryzby(at)telsasoft(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, rjuju123(at)gmail(dot)com, jakub(dot)wartak(at)tomtom(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: In-placre persistance change of a relation |
Date: | 2024-05-28 23:49:45 |
Message-ID: | CAGECzQRQzpE-EzJszHHvku1JLw+opu+KxE7rBqfyTmmgFwxrRQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 24 May 2024 at 00:09, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> Along with rebasing, I changed the interface of XLogFsyncFile() to
> return a boolean instead of an error message.
Two notes after looking at this quickly during the advanced patch
feedback session:
1. I would maybe split 0003 into two separate patches. One to make SET
UNLOGGED fast, which seems quite easy to do because no WAL is needed.
And then a follow up to make SET LOGGED fast, which does all the
XLOG_FPI stuff.
2. When wal_level = minital, still some WAL logging is needed. The
pages that were changed since the last still need to be made available
for crash recovery.
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2024-05-29 01:06:21 | Re: DROP OWNED BY fails to clean out pg_init_privs grants |
Previous Message | Andres Freund | 2024-05-28 22:13:50 | Re: meson vs windows perl |