Re: [HACKERS] case_preservation_and_insensitivity = on - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] case_preservation_and_insensitivity = on
Date
Msg-id 10691.1487224430@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] case_preservation_and_insensitivity = on  (Joel Jacobson <joel@trustly.com>)
Responses Re: [HACKERS] case_preservation_and_insensitivity = on  (Joel Jacobson <joel@trustly.com>)
List pgsql-hackers
Joel Jacobson <joel@trustly.com> writes:
> Case Preservation + Case Insensitivity = A good combination
> Thoughts?

Have you read any of our innumerable previous discussions about this?
The last one was barely a month ago, cf
https://www.postgresql.org/message-id/flat/ACF85C502E55A143AB9F4ECFE960660A17282D%40mailserver2.local.mstarlabs.com
https://www.postgresql.org/message-id/flat/CA%2BTgmoYcDXCp5E-2ga2%2BbBz%3DcdQN6T_bBDXksiggm6BtR7UA1A%40mail.gmail.com
(somehow the thread got broken in two in the archives)

The short answer is that nobody can see a way to modify the identifier
case-folding rules that isn't going to add more pain than it subtracts.
And much of the added pain will be felt by people who aren't getting
any benefit, who will therefore be vociferously against the whole thing.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] patch: function xmltable
Next
From: "Karl O. Pinc"
Date:
Subject: Re: [HACKERS] Patch to implement pg_current_logfile() function