| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Nicolas Seinlet <nicolas(at)seinlet(dot)eu>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: wal_init_zero / wal_recycle |
| Date: | 2024-04-24 08:57:21 |
| Message-ID: | 6a09dfdd-9dc5-49f4-82ea-826162ed0d74@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 24.04.24 10:08, Nicolas Seinlet wrote:
> while searching the doc to solve an issue, I found the interdependency
> between those 2 parameters was not obvious.
>
> Here:
> https://www.postgresql.org/docs/14/runtime-config-wal.html#GUC-WAL-INIT-ZERO <https://www.postgresql.org/docs/14/runtime-config-wal.html#GUC-WAL-INIT-ZERO>
>
> the wal_init_zero set to ON cause new WAL files to be filled with zeroes.
>
> It was not crystal clear to me that when wal_recycle is also ON , the
> recycled files are not filled with zeroes, because they are not
> considered as new. Could we add a sentence stating this?
It currently says:
wal_init_zero: "... causes new WAL files to be filled with zeroes ..."
wal_recycle: "... avoiding the need to create new ones ..."
I'm not sure where exactly to make that more clear.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nicolas Seinlet | 2024-04-24 09:17:21 | Re: wal_init_zero / wal_recycle |
| Previous Message | Nicolas Seinlet | 2024-04-24 08:08:21 | wal_init_zero / wal_recycle |