Re: More robust pg_hba.conf parsing/error logging

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: More robust pg_hba.conf parsing/error logging
Дата
Msg-id 1336.1252509807@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: More robust pg_hba.conf parsing/error logging  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: More robust pg_hba.conf parsing/error logging  (Stephen Frost <sfrost@snowman.net>)
Re: More robust pg_hba.conf parsing/error logging  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-hackers
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".

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".
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Rafael Martinez
Дата:
Сообщение: Re: More robust pg_hba.conf parsing/error logging
Следующее
От: Marko Kreen
Дата:
Сообщение: Re: [rfc] unicode escapes for extended strings