Re: BUG #5118: start-status-insert-fatal

From: Pedro Gimeno <pgsql-003(at)personal(dot)formauri(dot)es>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org, Gerhard Leykam <gel123(at)sealsystems(dot)de>
Subject: Re: BUG #5118: start-status-insert-fatal
Date: 2009-10-15 22:30:52
Message-ID: 4AD7A29C.3050008@personal.formauri.es
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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?

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Douglas, Ryan 2009-10-15 23:07:38 Re: BUG #5121: Segmentation Fault when using pam w/ krb5
Previous Message Tom Lane 2009-10-15 22:07:08 Re: BUG #5121: Segmentation Fault when using pam w/ krb5