You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a database is created by the container's entrypoint, it uses the default collation that will be en_US.utf8.
As discussed here: odoo/odoo#25196 (comment), this may be under-optimized with the use of LIKE queries using wildcards (LIKE 'foo%').
We have several possible axes of improvements:
add text_pattern_ops case by case where necessary
add trigram indices using pg_trgm which benefits for LIKE '%foo%' queries as well, case by case too however
create the databases with a C collation and locale en_US.utf8 (collate=C)
This is mainly the last point which should be discussed here.
Pros:
consistent sorting
expected general improvement of performance
Cons:
sorting of accented chars "sounds" wrong for French: Blanche, Béatrice, Claude is going to be sorted as Blanche, Béatrice, Claude instead of Béatrice, Blanche, Claude. Can be resolved with unaccent
My proposal is to change the calls to createdb in the image to always create them with collate=C.
The text was updated successfully, but these errors were encountered:
@sebastienbeau@rvalyi would you agree with this change?
An alternative would be to be able to configure it from a variable, but if the change is fine for everybody, let's keep it simple :)
When a database is created by the container's entrypoint, it uses the default collation that will be en_US.utf8.
As discussed here: odoo/odoo#25196 (comment), this may be under-optimized with the use of LIKE queries using wildcards (LIKE 'foo%').
We have several possible axes of improvements:
This is mainly the last point which should be discussed here.
Pros:
Cons:
My proposal is to change the calls to
createdb
in the image to always create them with collate=C.The text was updated successfully, but these errors were encountered: