Re: More robust pg_hba.conf parsing/error logging

Robert Haas wrote:
> On Tue, Feb 23, 2010 at 12:22 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Tom Lane wrote:
> >> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> >> > Andrew Dunstan wrote:
> >> >> It will affect any dbname or username in mixed or upper case, not just
> >> >> ALL, won't it?
> >>
> >> > No, I am suggesting to change only the comparisons to the literals
> >> > "all", "sameuser", "samegroup" and "samerole".
> >
> > What happened to this idea?
> >
> >> Hmm. ?These words are effectively keywords, so +1 for treating them
> >> case-insensitively, as we do in SQL. ?But I wonder whether there isn't
> >> an argument for making the comparisons of role and database names
> >> behave more like SQL, too --- that is FOO matches foo but not "FOO".
> >
> > And this one?
>
> Nobody's implemented them? I'd suggest adding these to the TODO.

Added:

|Process pg_hba.conf keywords as case-insensitive

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
PG East: http://www.enterprisedb.com/community/nav-pg-east-2010.do
+ If your life is a hard drive, Christ can be your backup. +