Re: Purpose of wal_init_zero - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: Purpose of wal_init_zero
Date
Msg-id CAJ7c6TMdLtaX-C-vNK0ffmprcRkzDGPyAPmf1xN5PrALJbAkJQ@mail.gmail.com
Whole thread Raw
In response to Re: Purpose of wal_init_zero  (Michael Banck <mbanck@gmx.net>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Sumanth Vishwaraj
Date:
Subject: Re: New feature request for adding session information to PostgreSQL transaction log
Next
From: Bertrand Drouvot
Date:
Subject: Re: per backend I/O statistics