From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Daniel Verite <daniel@manitou-mail.org>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: insensitive collations
Date: Wed, 19 Dec 2018 16:41:48 -0500
Message-ID: <11565.1545255708@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-WznTeqBL=cX8_V2AaQFBoeiecMPcw__27oEXEb4J_vDuzw@mail.gmail.com>
References: <39af4787-8042-4891-887c-3283488735db@manitou-mail.org>
<9502.1545230159@sss.pgh.pa.us>
<CAH2-WznTeqBL=cX8_V2AaQFBoeiecMPcw__27oEXEb4J_vDuzw@mail.gmail.com>
Peter Geoghegan <pg@bowt.ie> writes:
> The Unicode consortium calls our current behavior within comparisons
> "deterministic comparisons" -- it's something they're not so keen on:
> https://unicode.org/reports/tr10/#Deterministic_Comparison
> I suggest using their terminology for our current behavior.
Hm, it's not the greatest terminology perhaps, but if they're using it
then that makes it at least semi-standard. I can live with that.
> FWIW, I don't think that your IEEE analogy quite works, because you're
> talking about a property of a datatype. A collation is not intrinsic
> to any collatable datatype. Fortunately, we're not required to agree
> on what feels natural.
Right, which is exactly why it'd be a bad idea to use "natural" as the
name for this property ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, daniel@manitou-mail.org, peter.eisentraut@2ndquadrant.com
Subject: Re: insensitive collations
In-Reply-To: <11565.1545255708@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox