| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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: | 2010-02-23 18:22:03 |
| Message-ID: | 603c8f071002231022v59b43c28y12029d8f03b7c1e8@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 23, 2010 at 12:22 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Tom Lane wrote:
>> Alvaro Herrera <alvherre(at)commandprompt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-02-23 18:23:37 | Re: Adding \ev view editor? |
| Previous Message | Josh Berkus | 2010-02-23 18:21:02 | Re: [PATCH] 8.5 TODO: Add comments to output indicating version of pg_dump and of the database server |