pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Robert Treat <rob@xzilla.net>
To: David G. Johnston <david.g.johnston@gmail.com>
Cc: Euler Taveira <euler@eulerto.com>
Cc: Theodor Herlo <t.herlo@proventa.de>
Cc: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: Documentation for initdb option --waldir
Date: Sat, 29 Mar 2025 17:26:14 +0100
Message-ID: <990b0bfa9ad2e68c517c3d5a29c48d37758877a1.camel@cybertec.at> (raw )
In-Reply-To: <CAJSLCQ3J31T0VrKZ+Ad1qBvECmEFByfY5JrJ6z2bX=8OnN+GZg@mail.gmail.com >
References: <174291831170.676.262776479364497352@wrigleys.postgresql.org >
<CAKFQuwba2Rmf4X5yAkxARyy8X=Lv_4sN9vE7Z5exJji3d+7M2g@mail.gmail.com >
<1f38ffb000b9ead35702a63191c28f36e259c7d1.camel@cybertec.at >
<FR3P281MB19197329968C1F5D6537C6D5F6A12@FR3P281MB1919.DEUP281.PROD.OUTLOOK.COM >
<eeb6331a-dd43-4ddf-b378-f59e0fd2c1d7@app.fastmail.com >
<CAKFQuwbenWrFVa-BkzkHy9RFvFUQzzo=kDBTjikKfurxAse0cw@mail.gmail.com >
<CABV9wwN8nafxG8MdfEuHPxMhxr9SmGAoWKLBNr=9Ja6q9=1N+Q@mail.gmail.com >
<CAKFQuwYpmEUDVw2DTCs0v4J3g20BmZq_5HYgjpcFQfDt4Yy2+w@mail.gmail.com >
<CAJSLCQ3J31T0VrKZ+Ad1qBvECmEFByfY5JrJ6z2bX=8OnN+GZg@mail.gmail.com >
On Sat, 2025-03-29 at 10:26 -0400, Robert Treat wrote:
> "Best practice is to create a directory within the mount-point
> directory that is owned by the PostgreSQL user, and then create the
> data directory within that. This avoids permissions problems,..."
>
> Which I do remember having tried to do it directly and the OS
> complaining that my mount point wasn't owned by root and/or Postgres
> complaining that the xlog dir wasn't owned by Postgres, so I think
> this advice probably still holds.
The root directory of a file system, which will be mounted at the
mount point, should be owned by root.
As far as I know, the reason is that it contains a "lost+found"
directory, which is used by file system checks to put orphaned
files. If a non-root user owned the mount point, the user could
remove that directory, which would be a bad idea.
On the other hand, PostgreSQL will protest if the directory isn't
empty...
Yours,
Laurenz Albe
view thread (14+ messages) latest in thread
Message-ID: <990b0bfa9ad2e68c517c3d5a29c48d37758877a1.camel@cybertec.at>
Permalink: ../990b0bfa9ad2e68c517c3d5a29c48d37758877a1.camel@cybertec.at/
Also on: postgresql.org/message-id/990b0bfa9ad2e68c517c3d5a29c48d37758877a1.camel@cybertec.at
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, rob@xzilla.net, david.g.johnston@gmail.com, euler@eulerto.com, t.herlo@proventa.de, pgsql-docs@lists.postgresql.org
Subject: Re: Documentation for initdb option --waldir
In-Reply-To: <990b0bfa9ad2e68c517c3d5a29c48d37758877a1.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox