Re: Making pg_hba.conf case-insensitive

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making pg_hba.conf case-insensitive
Date: 2016-08-20 17:43:58
Message-ID: 20160820174358.GC21840@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 18, 2016 at 04:49:04PM -0400, Bruce Momjian wrote:
> On Thu, Aug 18, 2016 at 03:01:48PM -0400, Peter Eisentraut wrote:
> > On 8/18/16 1:59 PM, Bruce Momjian wrote:
> > > o compares words in columns that can only support keywords as
> > > case-insensitive, double-quoted or not
> > >
> > > o compares words in columns that can contain user/db names or keywords
> > > as case-sensitive if double-quoted, case-insensitive if not
> >
> > I can maybe see the case of the second one, but the first one doesn't
> > make sense to me.
> >
> > We've in the past had discussions like this about whether command line
> > arguments of tools should be case insensitive like SQL, and we had
> > resolved that since the shell is not SQL, it shouldn't work like that.
> > pg_hba.conf is also not SQL, and neither, for that matter, is
> > pg_ident.conf and postgresql.conf.
>
> OK, I am happy to remove the TODO item and see if we get new complaints.

TODO item removed.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-08-20 18:02:30 Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)
Previous Message Tom Lane 2016-08-20 17:25:49 Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)