Re: Set arbitrary GUC options during initdb

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Robert Haas <robertmhaas@gmail.com>, "David G. Johnston" <david.g.johnston@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2023-03-22T20:07:51Z

Lists: pgsql-hackers

Hi,

This commit unfortunately broke --wal-segsize. If I use a slightly larger than
the default setting, I get:

initdb --wal-segsize 64 somepath
running bootstrap script ... 2023-03-22 13:06:41.282 PDT [639848] FATAL:  "min_wal_size" must be at least twice "wal_segment_size"

Greetings,

Andres Freund

Commits

Fix initdb's handling of min_wal_size and max_wal_size.
- b48af6d174bb 16.0 landed
Reduce memory leakage in initdb.
- 4fe2aa7656dc 16.0 landed
Add "-c name=value" switch to initdb.
- 3e51b278db6a 16.0 landed