> But in actual practise, there is a problem, postgresql.auto.conf is
> stored inside PGDATA, which is not readable by anyone except postgres
> and root, so settings modified that way are only visible (and used)
> for these users.
ok, thank you for the clarification Christoph,
root and postgres do indeed give the correct information,
other users don't.
>
> I don't see how we can sanely get out of this problem. The idea of
> connecting to the server to query pg_settings has the problem that
> it's more heavyweight, and of course we need to know the port to be
> able to connect... Storing the port in yet another location doesn't
> seem attractive either.
if i compare the permission settings of the 2 conf files:
-rw-r--r-- 1 postgres postgres 22983 feb 14 12:45
/etc/postgresql/11/oefensets/postgresql.conf
-rw------- 1 postgres postgres 385 mrt 2 2018
/var/lib/postgresql/11/oefensets/postgresql.auto.conf
why are they different? if it's important that postgresql.auto.conf
isn't readable by other, then why is postgresql.conf,
if it is an option: storing the postgresql.auto.conf in the
/etc/postgresql/11/oefensets/ dir would open the option to set the
permissions to -rw-r--r--
Or is there a good reason not to store this file here?
>
> Christoph
--
mvg,
Wim Bertels
--
If more of us valued food and cheer and song above hoarded gold, it would
be a merrier world.
-- J.R.R. Tolkien
