From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: keywords in initdb are case-sensitive? |
Date: | 2012-02-02 14:39:29 |
Message-ID: | CA+TgmoZ3v2bag2kFacKLHipq-9xsCgbqb5cz0_Xu+FCWPyNWNQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Feb 1, 2012 at 11:45 PM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> In miracee's review of Peter's patch for new -A options in initdb (in
> commitfest app only), it is noted that pg_hba.conf keyword parsing is
> done in a case sensitive manner. So if you write "Trust" rather than
> "trust", it's not recognized.
>
> This seemed pretty nonsensical to me, and it's not documented, so I came
> up with the trivial attached patch.
>
> Comparisons to user and database names and the like are unchanged and
> thus require matching case.
>
> Thoughts?
We have lots of things that are case-sensitive; I don't particularly
see why this one should be different.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-02-02 14:41:46 | Re: patch for implementing SPI_gettypemod() |
Previous Message | Marko Kreen | 2012-02-02 14:30:57 | Re: Speed dblink using alternate libpq tuple storage |