se it aren't confronted with errors about things that don't matter to
them. I welcome suggestions that can move us closer to that goal
without breaking previously-working commands.
Regards,
Jeff Davis
;d like to force LC_COLLATE=C and LC_CTYPE=C, and then there'd be no
question, but I won't promise when that will happen. I'd suggest just
forcing those to "C" in your database.
Regards,
Jeff Davis
[1] https://www.unicode.org/policies/stability_policy.html
ting a database; along with the builtin provider
and UTF-8 as you are already doing.
Regards,
Jeff Davis
stance, there's a collation named "en_US" in
pg_collation, which points to the libc provider and locale name
'en_US.utf8'. There's also a collation named "en-US-x-icu" in
pg_collation which points to the ICU provider and locale name 'en-US'.
In other words, the collation objects are a layer of indirection to
what the provider actually understands.
Regards,
Jeff Davis
