| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Encoding/collation question |
| Date: | 2019-12-18 09:37:35 |
| Message-ID: | 20191218093735.GA472@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Dec 12, 2019 at 08:35:53AM -0500, Tom Lane wrote:
> C collation basically devolves to strcmp/memcmp, which are as standard
> and well-defined as can be. If you're happy with the way it sorts
> things then there's no reason not to use it.
So that's the collation to use when "technical" sorting is
required (say, when uniqueness does not depend on the notion
of culturally equivalent characters).
> It's actually all the *other* collations where you should worry about
> their behavior being a moving target :-(.
But then that is to be expected.
Thanks,
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
| From | Date | Subject | |
|---|---|---|---|
| Next Message | James (王旭) | 2019-12-18 09:53:26 | How to prevent POSTGRES killing linux system from accepting too much inserts? |
| Previous Message | Kaijiang Chen | 2019-12-18 03:25:32 | Fwd: weird long time query |