Re: More robust pg_hba.conf parsing/error logging
От | Robert Haas |
---|---|
Тема | Re: More robust pg_hba.conf parsing/error logging |
Дата | |
Msg-id | 603c8f071002231022v59b43c28y12029d8f03b7c1e8@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: More robust pg_hba.conf parsing/error logging (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: More robust pg_hba.conf parsing/error logging
|
Список | pgsql-hackers |
On Tue, Feb 23, 2010 at 12:22 AM, Bruce Momjian <bruce@momjian.us> wrote: > 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? Nobody's implemented them? I'd suggest adding these to the TODO. ...Robert
В списке pgsql-hackers по дате отправления: