From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brendan Jurd <direvus(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fwd: Keywords in pg_hba.conf should be field-specific |
Date: | 2011-06-21 16:41:11 |
Message-ID: | 1308674409-sup-1729@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Pavel Stehule's message of mar jun 21 11:04:11 -0400 2011:
> 2011/6/21 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> > AFAICS, this is only important in places where the syntax allows either
> > a keyword or an identifier. If only a keyword is possible, there is no
> > value in rejecting it because it's quoted. And, when you do the test,
> > I think you'll find that it would be breaking hba files that used to
> > work (though admittedly, it's doubtful that there are any such in the
> > field).
>
> It should be better documented. I don't think so this is good
> solution, but this is not too important.
On the contrary -- we should support it but not document it. I mean,
what good would that do? If someone is so silly to uselessly quote
keywords, let them do it, but let's not encourage it.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-06-21 17:07:17 | Re: Table Partitioning |
Previous Message | Alexey Klyukin | 2011-06-21 15:31:44 | Re: Identifying no-op length coercions |