Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>
Cc: solai v <solai(dot)cdac(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>
Subject: Re: Add a pg_wal_preallocate() SQL function to eagerly create future WAL segments
Date: 2026-08-03 11:07:48
Message-ID: CAN55FZ20jSerxR5D2LX_BKdXHPVqPdNtMNsWr3nT81hJBJh5LA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Thank you for working on this!

On Mon, 3 Aug 2026 at 08:13, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com> wrote:
>
> Hi,
>
> Rebased patch attached.

Patch LGTM, it works as intended. My only concern is the unbounded max
limit; which can cause problems. I think 'max_wal_size' is a
reasonable limit. Perhaps we can add a 'force' boolean option to
function, then it can bypass the 'max_wal_size' limit; what do you
think?

--
Regards,
Nazir Bilal Yavuz
Microsoft

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-08-03 11:09:32 Re: Return DSA area for hash table from GetNamedDSHash()
Previous Message shveta malik 2026-08-03 10:41:01 Re: A new C function `get_partition_root`.