Re: Making pg_hba.conf case-insensitive

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Making pg_hba.conf case-insensitive
Date: 2016-08-18 18:48:31
Message-ID: 20160818184831.GA6881@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 18, 2016 at 02:06:39PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I was looking at this TODO item from 2009:
> > https://www.postgresql.org/message-id/4AA7B197.70002%40usit.uio.no
> > I have implemented this in the attached patch. It does two things:
>
> Is there really enough demand for this to justify subtle breakage
> of existing pg_hba.conf entries? It'd probably have been fine if
> we did it like that originally, but I think it's a bit late now.

Well, in 2009 the discussion was whether to backpatch or not, which
seems a long way from saying we can't change it in a major release:

https://www.postgresql.org/message-id/1336.1252509807%40sss.pgh.pa.us
https://www.postgresql.org/message-id/5060.1252523065%40sss.pgh.pa.us

It is certainly something we can discuss.

> Also, why strcasecmp and not pg_strcasecmp? The former is going
> to induce misbehavior in e.g. Turkish locales.

OK, changed, and attached.

--
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 +

Attachment Content-Type Size
hba.diff text/x-diff 18.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2016-08-18 18:49:19 Re: anyelement -> anyrange
Previous Message Stefan Kaltenbrunner 2016-08-18 18:45:55 Re: WIP: About CMake v2