Re: Purpose of wal_init_zero

Hi,

On Wed, Jan 15, 2025 at 09:12:17AM +0000, Andy Fan wrote:
> I can understand that "the file space has really been allocated", but
> why do we care about this?
>
> One reason I can think of is it has something with "out-of-disk-space"
> sistuation, even though what's the benefit of it since we can't do
> anything in such case anyway no matter the wal space is pre-alocated or
> not?

My understanding was that if we have pre-allocated wal space (and
re-cycle already used wal files), we can still write wal records into
that pre-allocated space and still issue changes to data files as long
as we don't need to enlarge any. So an out-of-space situation is less
bad in that case than if we fail to write WAL with ENOSPC.

Michael