Re: Purpose of wal_init_zero

From: Andy Fan <zhihuifan1213(at)163(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Ritu Bhandari <mailritubhandari(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Purpose of wal_init_zero
Date: 2025-01-21 01:09:09
Message-ID: 87y0z53rd6.fsf@163.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hi,

> On Fri, Jan 17, 2025 at 04:29:14PM -0500, Andres Freund wrote:
>> I think what we instead ought to do is to more aggressively initialize WAL
>> files ahead of time, so it doesn't happen while holding crucial locks. We
>> know the recent rate of WAL generation, and we could easily track up to which
>> LSN we have recycled WAL segments. Armed with that information walwriter (or
>> something else) should try to ensure that there's always a fair amount of
>> pre-allocated WAL.
>
> I put some patches together for this a few years ago [0], but ended up
> abandoning them due to lack of interest. I'm happy to revisit that effort
> if folks do become interested.

Great to know this, I went through that thread and found the main
considerations are pretty similar with what I am thinking when working
out the Poc. I will go to [0] for further dicussion on this topic.

> [0] https://postgr.es/m/20220408203003.GA1630183%40nathanxps13
--
Best Regards
Andy Fan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2025-01-21 01:20:53 Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options
Previous Message Jeremy Schneider 2025-01-21 01:06:29 Re: Update Unicode data to Unicode 16.0.0