Aw: Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all" - Mailing list pgsql-general

From Karsten Hilbert
Subject Aw: Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"
Date
Msg-id trinity-ef283834-3777-4429-a224-564a8e380707-1667319301502@3c-app-gmx-bap64
Whole thread Raw
In response to Re: Putting the O/S user for "local" "peer" authentication in the "postgres" group vs chmod'ing the "pg*.conf" files to be readable by "all"  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-general
> The client user should *never* read the PostgreSQL configuration files, so if changing
> the permissions (which you should *never* do) has an effect, you must be doing something
> very strange, like trying to start the database server with the wrong user.

It smells of trying to *embed* PostgreSQL ?

But that would not go with the account of multi-tenancy that's been presented.

Karsten



pgsql-general by date:

Previous
From: Ron
Date:
Subject: SSL/TLS encryption without
Next
From: "Peter J. Holzer"
Date:
Subject: Re: SSL/TLS encryption without