Emanuel Calvo Franco <postgres....@gmail.com> writes:
> 2009/3/10 Gregory Stark <st...@enterprisedb.com>:
>> Tom Lane <t...@sss.pgh.pa.us> writes:
>>> However, a tip that might help is that there should be more information
>>> about the problem in the postmaster log. We intentionally don't send
>>> details about the conf file's contents to the client...
>>
>> Perhaps we should send a HINT to the client saying to consult the postmaster
>> logs?
egg on my face -- we already *do* have such a hint:
ereport(FATAL,
(errcode(ERRCODE_CONFIG_FILE_ERROR),
errmsg("missing or erroneous pg_hba.conf file"),
errhint("See server log for details.")));
> IMHO I think is quite dangerous because someone with experience could guess
> some security details.
How?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
