Re: Fwd: Keywords in pg_hba.conf should be field-specific
От | Alvaro Herrera |
---|---|
Тема | Re: Fwd: Keywords in pg_hba.conf should be field-specific |
Дата | |
Msg-id | 1308664578-sup-6011@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Fwd: Keywords in pg_hba.conf should be field-specific (Pavel Stehule <pavel.stehule@gmail.com>) |
Ответы |
Re: Fwd: Keywords in pg_hba.conf should be field-specific
Re: Fwd: Keywords in pg_hba.conf should be field-specific |
Список | pgsql-hackers |
Excerpts from Pavel Stehule's message of mar jun 21 00:59:44 -0400 2011: > yes - it has a sense. Quoting changes sense from keyword to literal. > But then I see a significant inconsistency - every know keywords > should be only tokens. > > else if (strcmp(token, "pamservice") == 0) > - { > - REQUIRE_AUTH_OPTION(uaPAM, "pamservice", "pam"); > - parsedline->pamservice = pstrdup(c); > - } > > because >>pamservice<< - is known keyword, but 'pamservice' is some > literal without any mean. You should to use a makro token_is_keyword > more often. Yeah, I wondered about this too (same with auth types, i.e. do we accept quoted "hostssl" and so on or should that by rejected?). I opted for leaving it alone, but maybe this needs to be fixed. (Now that I think about it, what we should do first is verify whether it works with quotes in the unpatched code). -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: