Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS) - Mailing list pgsql-general

From Laurenz Albe
Subject Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
Date
Msg-id 0b3fb11184bf9ce6516ed1aa08af5dddc924f21c.camel@cybertec.at
Whole thread Raw
In response to Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)  (Amol Inamdar <amol.aai@gmail.com>)
Responses Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
List pgsql-general
On Mon, 2025-07-14 at 17:59 +0530, Amol Inamdar wrote:
> If I am not mistaken, below is my understanding of your suggestion. 
>
> Suppose that My mount point on the NFS server is say /nfs-mount/postgres/ 
> and you are suggesting to have a data directory as say /nfs-mount/postgres/db or something like that ? 
> and assign this value to the PGDATA ? 
>
> If that is the case, then when and who should be creating the directory DB ? 
>
> Please correct me if I am wrong about the understanding.

You understood me perfectly well.

The data directory can either be created by "initdb", in which case
the mount point must allow the PostgreSQL user to create a directory.
You could set the group of the mount point to the group of the
PostgreSQL user and use permissions 1770, which should be perfectly safe.

Alternatively, the root user could create the data directory with the
correct ownership and permissions prior to running "initdb".

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Amol Inamdar
Date:
Subject: Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
Next
From: Amol Inamdar
Date:
Subject: Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)