pgsql: Fix initdb's handling of min_wal_size and max_wal_size. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix initdb's handling of min_wal_size and max_wal_size.
Date
Msg-id E1pf5DM-004sq5-NF@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Fix initdb's handling of min_wal_size and max_wal_size.

In commit 3e51b278d, I misinterpreted the coding in setup_config()
as setting min_wal_size and max_wal_size to compile-time-constant
values.  But it's not: there's a hidden dependency on --wal-segsize.
Therefore leaving these variables commented out is the wrong thing.
Per report from Andres Freund.

Discussion: https://postgr.es/m/20230322200751.jvfvsuuhd3hgm6vv@awork3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b48af6d174bb39bd688d52795aef2b9c10dd6e8c

Modified Files
--------------
src/bin/initdb/initdb.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)


pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgsql: Teach verify_heapam() to validate update chains within a page.
Next
From: Tom Lane
Date:
Subject: pgsql: Fix new test case to work on (some?) big-endian architectures.