Re: BUG #5118: start-status-insert-fatal - Mailing list pgsql-bugs

From Pedro Gimeno
Subject Re: BUG #5118: start-status-insert-fatal
Date
Msg-id 4AD7A29C.3050008@personal.formauri.es
Whole thread Raw
In response to Re: BUG #5118: start-status-insert-fatal  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #5118: start-status-insert-fatal
List pgsql-bugs
Tom Lane wrote:

> This could be addressed by having the postmaster report its $PGDATA
> value in the pg_ping response, but I would be against that on security
> grounds.  We don't let nonprivileged users know where PGDATA is, why
> would we make the information available without any authentication at
> all?

Maybe a hash of it?

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #5121: Segmentation Fault when using pam w/ krb5
Next
From: Jesse Morris
Date:
Subject: Re: BUG #5065: pg_ctl start fails as administrator, with "could not locate matching postgres executable"