From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | t(dot)herlo(at)proventa(dot)de, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Documentation for initdb option --waldir |
Date: | 2025-03-27 00:34:44 |
Message-ID: | CAKFQuwba2Rmf4X5yAkxARyy8X=Lv_4sN9vE7Z5exJji3d+7M2g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Wed, Mar 26, 2025 at 2:35 AM PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/17/app-initdb.html
> Description:
>
> Hi all,
>
> During troubleshooting with a customer we found that it might help to know
> that initdb will create a symbolic link from data/pg_wal to the custom
> directory with the option --waldir.
>
>
Thank you for the observation. This indeed seems like something we should
cover in a bit more detail. How does the proposed patch (attached) look?
The main initdb change, added to Notes, is:
The pg_wal subdirectory will always exist within the data directory. This
is where PostgreSQL sends its write-ahead log (WAL) files. Specifying the
--waldir option turns this subdirectory entry into a symbolic link. In
general, this is only useful if the remote location is on a different
physical device. An existing directory must be empty and should not be a
mount point. The directory will be created (including missing parents) if
necessary.
David J.
Attachment | Content-Type | Size |
---|---|---|
v1-0001-doc-Explain-use-of-symbolic-linking-for-pg_wal.patch | text/x-patch | 2.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-03-27 10:32:18 | Re: Documentation for initdb option --waldir |
Previous Message | PG Doc comments form | 2025-03-25 15:58:31 | Documentation for initdb option --waldir |