initdb help message about WAL segment size

Started by Magnus Haganderover 8 years ago2 messageshackers
Beta feature

Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

won't retrysuccessCI history

You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:

docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t38354
psql -h localhost -U postgres

Built from patchset v1 (message #1), July 27, 2026 at 08:57 PM.

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t38354_1 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t38354_1 && git checkout t38354_1

Patchset v1 (message #1) is on t38354_1

Jump to latest
#1Magnus Hagander
magnus@hagander.net

I propose the attached patch, aligning the help message with the docs. Any
reason not to?

(yes, I confused myself by trying --wal-segsize=1MB instead of just
--wal-segsize=1. I blame just stepping off an intercontinental flight and a
very early morning :P)

--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/&gt;
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/&gt;

Attachments:

t38354_1
walsegsize.patchtext/x-patch; charset=US-ASCII; name=walsegsize.patchDownload+1-1
#2Michael Paquier
michael@paquier.xyz
In reply to: Magnus Hagander (#1)
Re: initdb help message about WAL segment size

On Sun, Mar 11, 2018 at 08:23:39AM +0100, Magnus Hagander wrote:

I propose the attached patch, aligning the help message with the docs. Any
reason not to?

+1 for doing what you are suggesting.
--
Michael