| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joel Jacobson <joel(at)trustly(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: case_preservation_and_insensitivity = on |
| Date: | 2017-02-16 05:53:50 |
| Message-ID: | 10691.1487224430@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joel Jacobson <joel(at)trustly(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl O. Pinc | 2017-02-16 05:55:58 | Re: Patch to implement pg_current_logfile() function |
| Previous Message | Pavel Stehule | 2017-02-16 05:38:04 | Re: patch: function xmltable |