Investigate use of C locale and collation to speedup index creation in HAF
dan 12:56 PM Do you know if we already use C locale and collation for postgres in HAF? found this article: https://dba.stackexchange.com/questions/99091/create-index-on-a-postgres-table-as-fast-as-possible
efrias 2:39 PM I think the answer is "no". If I'm reading it right, the collation for haf_block_log on steem-2 is set to C.UTF-8, and it seems there's a difference (C is sorted internally in postgresql, 'C.UTF-8` would be passed to a standard library function. There's also this bit in the HAF README.md:
Preparing a PostgreSQL database
The database should use these parameters: ENCODING = 'UTF8' LC_COLLATE = 'en_US.UTF-8' and LC_CTYPE = 'en_US.UTF-8' (this is default for american english locale, it's not tested on other locale configurations). which doesn't quite match what I see on steem-2, but it would also not be the C locale.
dan 2:40 PM ok, so I guess I'll bring this up as something we should consider in hive channel.
msobczyk 3:20 AM I remember that unit tests were failing when using different LC_COLLATE / LC_CTYPE and there is no other reason why we can't use C locale