Hi, On Mon, 3 Aug 2026 at 17:30, Ayush Tiwari <[email protected]> wrote:
> Hi, > > On Mon, 3 Aug 2026 at 16:38, Nazir Bilal Yavuz <[email protected]> wrote: > >> 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? >> > > Thanks for the review! I like the idea you suggested. > > Let me try implementing it that way. > v4 attached. By default the request is now limited to the whole segments that fit within max_wal_size, and force => true bypasses that when you really do want a bigger warm-up. A NOTICE is issued only when an explicit request is reduced; a plain no-argument call stays quiet. Regards, Ayush
v4-0001-pg_wal_preallocate.patch
Description: Binary data
