Re: pgsql: Add function to import operating system collations
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-committers@postgresql.org
Date: 2017-01-18T18:46:03Z
Lists: pgsql-hackers
I wrote: > The previous coding applied a sort so as not to depend on what > order "locale -a" had returned things in, and I think we need > to retain that. At the very least, all the normalized names > need to be saved up and entered in a second pass. Actually, it seems like doing precisely that should be enough to fix it. The original names shouldn't have any dups, and if we generate dup names by stripping, those will be for different encodings so it's OK. I've pushed a fix based on that. regards, tom lane
Commits
-
Avoid conflicts with collation aliases generated by stripping.
- 0333a7340054 10.0 landed
-
Add function to import operating system collations
- aa17c06fb585 10.0 cited
-
Remove dead code in bootstrap
- 193a7d791ebe 10.0 cited