Luis Felippe wrote: > This fix changes this call to pass UCOL_DEFAULT instead. This way, > UCOL_TERTIARY is still specified by default, but the strength explicitly set > on the rules string is not overwritten. This is important because there is > currently no way to create a collation with custom tailoring rules with > strengh other than tertiary.
Yes. There was a previous report recently [1], with a proposed fix [2] identical to yours. > As this only affects cases where the strength is explicitly set but was > previously ignores, I do not think it is a breaking change. The fix may change sort results for collations affected by the problem (that's the point of the fix!), so even if it's for the better, it's theorically a breaking change for databases that may have collations like that. [1] https://www.postgresql.org/message-id/flat/yt2ppf959236618377a072745a280e278f4be...@yt2ppf959236618.canprd01.prod.outlook.com [2] https://commitfest.postgresql.org/patch/6084/ Best regards, -- Daniel Vérité https://postgresql.verite.pro/
