From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Silent failure with invalid hba_file setting |
Date: | 2011-10-18 12:04:04 |
Message-ID: | CAA-aLv7ZvQDZqSjk4OpBcoxpXYEVrPNxMiFpHaB+HEMcdidFLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I noticed that if the hba_file setting in the config is uncommented
and set to a directory instead of the full path to the file, no error
occurs when the service starts.
For example:
hba_file = '/home/thom/Development/data'
The problem with this is you cannot get into the database as it acts
as if it did find the hba file but found it empty.
Shouldn't a check be in place to ensure that the parameter resolves to
a file rather than anything else? And even if it does find a file,
but it's empty, shouldn't it also produce a warning of some kind?
--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-10-18 12:13:11 | Re: (patch) regression diffs on collate.linux.utf8 test |
Previous Message | desmodemone | 2011-10-18 09:19:21 | Re: BUG or strange behaviour of update on primary key |