Re: More robust pg_hba.conf parsing/error logging - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: More robust pg_hba.conf parsing/error logging
Date
Msg-id 201002230522.o1N5M3d07312@momjian.us
Whole thread Raw
In response to Re: More robust pg_hba.conf parsing/error logging  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: More robust pg_hba.conf parsing/error logging
List pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.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?

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: A thought on Index Organized Tables
Next
From: Bruce Momjian
Date:
Subject: Re: Adding \ev view editor?