Re: BUG #15810: Using custom directory on external HDD givespermission error - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #15810: Using custom directory on external HDD givespermission error
Date
Msg-id 20190516234351.GC20887@paquier.xyz
Whole thread Raw
In response to BUG #15810: Using custom directory on external HDD gives permission error  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15810: Using custom directory on external HDD gives permission error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Thu, May 16, 2019 at 04:15:39PM +0000, PG Bug reporting form wrote:
> Is there some way to circumvent this check without changing format
> of the HDD?

That's weird.  If the data folder fed to initdb already exists and is
empty, then permissions on the path are enforced to 0700 or 0750 (if
using --allow-group-access) automatically to prevent this error when
starting Postgres for bootstrapping.  If the path does not exist, then
the data folder is created with proper permissions.  In any case, you
should not see this error.

Are you using some specific mounting options?
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: inconsistent results querying table partitioned by date
Next
From: Tom Lane
Date:
Subject: Re: BUG #15810: Using custom directory on external HDD gives permission error