why not using a mountpoint as PGDATA?

From: Luca Ferrari <fluca1978(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: why not using a mountpoint as PGDATA?
Date: 2019-02-27 11:21:40
Message-ID: CAKoxK+6H40imynM5P31bf0DnpN-5f5zeROjcaj6BKVAjxdEA9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I apparently cannot find an answer in the documentation, however initdb states:

initdb: directory "/mnt/data1" exists but is not empty
It contains a dot-prefixed/invisible file, perhaps due to it being a
mount point.
Using a mount point directly as the data directory is not recommended.
Create a subdirectory under the mount point.

and effectively /mnt/data1 is a mountpoint, therefore but belongs to
the user of the cluster, therefore the only difference I can see is
having '..' belonging to root at the mountpoint or the cluster user
within a subdirectory.
What's wrong with using a mountpoint?

Thanks,
Luca

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Julien Rouhaud 2019-02-27 11:33:02 Re: why not using a mountpoint as PGDATA?
Previous Message Sam Saffron 2019-02-27 10:11:37 Why can I not get lexemes for Hebrew but can get them for Armenian?