On 2019-09-09 19:15:19 +0200, Peter J. Holzer wrote:
> On 2019-09-09 10:03:57 -0400, Tom Lane wrote:
> > "Peter J. Holzer" writes:
> > > Yesterday I "apt upgrade"d patroni (to version 1.6.0-1.pgdg18.04+1
> > > from http://apt.postgresql.org/pub/repos/apt bionic-pgdg/main).
> > > Today I noticed th
On 2019-09-09 13:29:38 +0200, Daniel Verite wrote:
> Peter J. Holzer wrote:
> > 2) Why does psql need to read postgresql.conf, and more specifically,
> > why does it care about the location of the data directory? It
> > shouldn't access files directly, just talk to the server via the
> >
"Peter J. Holzer" writes:
> Yesterday I "apt upgrade"d patroni (to version 1.6.0-1.pgdg18.04+1 from
> http://apt.postgresql.org/pub/repos/apt bionic-pgdg/main).
> Today I noticed that I couldn't invoke psql as an unprivileged user
> anymore:
> % psql
> Error: Invalid data directory for cluster 11
Peter J. Holzer wrote:
> 2) Why does psql need to read postgresql.conf, and more specifically,
> why does it care about the location of the data directory? It
> shouldn't access files directly, just talk to the server via the
> socket.
It's not psql itself, it's pg_wrapper.
$ ls -l
Yesterday I "apt upgrade"d patroni (to version 1.6.0-1.pgdg18.04+1 from
http://apt.postgresql.org/pub/repos/apt bionic-pgdg/main).
Today I noticed that I couldn't invoke psql as an unprivileged user
anymore:
% psql
Error: Invalid data directory for cluster 11 main
Further investigation showed th
