| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Rafael Martinez <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More robust pg_hba.conf parsing/error logging |
| Date: | 2009-09-09 14:31:25 |
| Message-ID: | 20090909143125.GF4132@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Alvaro Herrera wrote:
> >Surely if you want to designate a database named ALL you should use
> >quotes, same as if you wanted to designate a database named all (see my
> >other followup).
>
> OK, but if we move to using pg_strcasecmp() that would be a
> behaviour change, so I think we couldn't do it before 8.5, in case
> someone is relying on it.
Yeah, I think so. It doesn't seem like this is backpatchable (I lean
towards doubting that anyone is using a database named ALL, but still).
> 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".
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-09-09 14:33:16 | Re: More robust pg_hba.conf parsing/error logging |
| Previous Message | Rafael Martinez | 2009-09-09 14:30:00 | Re: More robust pg_hba.conf parsing/error logging |