On Thu, Aug 18, 2016 at 02:06:39PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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@momjian.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 +
