Re: Documentation for initdb option --waldir

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Gurjeet Singh <gurjeet(at)singh(dot)im>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Robert Treat <rob(at)xzilla(dot)net>, Euler Taveira <euler(at)eulerto(dot)com>, Theodor Herlo <t(dot)herlo(at)proventa(dot)de>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Documentation for initdb option --waldir
Date: 2025-03-29 17:27:53
Message-ID: CAKFQuwZ491cadtbzyFaTHaXOqN69ysmTV3tzraNrLAK2vYKdMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Saturday, March 29, 2025, Gurjeet Singh <gurjeet(at)singh(dot)im> wrote:

> On Sat Mar 29, 2025 at 9:26 AM PDT, Laurenz Albe wrote:
>
> > On the other hand, PostgreSQL will protest if the directory isn't
> > empty...
>
> Specifically, initdb will complain if the directory it's trying to
> initialize is not empty.
>

For this patch I intend to just point the reader to the “secondary file
systems” section mentioned above for more considerations. We can improve
that as desired separately.

David J.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2025-03-31 10:29:28 SEQUENCE keyword is option on GRANT
Previous Message Gurjeet Singh 2025-03-29 17:12:19 Re: Documentation for initdb option --waldir