Re: BUG #15810: Using custom directory on external HDD gives permission error

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: omerfaruko(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15810: Using custom directory on external HDD gives permission error
Date: 2019-05-16 23:43:51
Message-ID: 20190516234351.GC20887@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-05-16 23:59:33 Re: BUG #15810: Using custom directory on external HDD gives permission error
Previous Message Tom Lane 2019-05-16 22:50:50 Re: inconsistent results querying table partitioned by date