On Wed, 2025-07-16 at 18:54 +0530, Amol Inamdar wrote: > I would like to rephrase the question a little bit, below is how our setup > going to be > 1. NFS mount point is for /nfs-mount/postgres (and permissions locked down > so > that Postgres cannot create directories in here) > 2. Postgres data directory is /nfs-mount/postgres/db > 3. With secured NFS + AT-TLS setup Postgres will be able to write to data > directory > but not parent dir, however the file ownership information Postgres > sees from the > stat() call will not match the Postgres user in the container (even > though the > AT-TLS strict access control will ensure only the Posgres user can > read/write to > this directory) > Considering the above scenario/setup, what is the danger of removing the > ownership check > in miscinit.c checkDataDir() function ?
The danger is that somebody else than the PostgreSQL user has permissions on the data directory. You will argue that that somebody is root, and root has these permissions anyway. But there is another reason why PostgreSQL insists that the PostgreSQL user owns the data directory: at startup, the postmaster checks if the data directory belongs to the current user and fails if not. This is a protection against starting the postmaster with the wrong user. There are certainly ways to do it differently, but I'd argue that they would be more complicated, and the current simple solution is robust. If you pre-create the data directory with the appropriate permissions, what keeps you from giving ownership to the correct user too? Yours, Laurenz Albe
