Fix initdb's handling of min_wal_size and max_wal_size.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 22 Mar 2023 20:37:41 +0000 (16:37 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 22 Mar 2023 20:37:41 +0000 (16:37 -0400)
commitb48af6d174bb39bd688d52795aef2b9c10dd6e8c
tree6945ad0fa36aab65e7bd65e6168343b7bb5028a8
parent4fe2aa7656dce2bd31d4807a6843ff495b9deb80
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
src/bin/initdb/initdb.c