Re: Purpose of wal_init_zero

Hi Michael,

> 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.

True, but if we are out of space we are going to crash anyway because
we can't allocate new heap pages, write regular (text) logfiles,
update CLOG and other SLRU-based structures, etc. So if it is "less
bad" the difference seems to be negligible - either way you crash.
Unless I'm missing something of course.

--
Best regards,
Aleksander Alekseev