mirror of https://github.com/postgres/postgres
parent
4baff50132
commit
2b03cfeea4
|
@ -1922,16 +1922,16 @@ varstr_sortsupport(SortSupport ssup, Oid typid, Oid collid)
|
||||||
* Unfortunately, it seems that abbreviation for non-C collations is
|
* Unfortunately, it seems that abbreviation for non-C collations is
|
||||||
* broken on many common platforms; see pg_strxfrm_enabled().
|
* broken on many common platforms; see pg_strxfrm_enabled().
|
||||||
*
|
*
|
||||||
* Even apart from the risk of broken locales, it's possible that there
|
* Even apart from the risk of broken locales, it's possible that
|
||||||
* are platforms where the use of abbreviated keys should be disabled at
|
* there are platforms where the use of abbreviated keys should be
|
||||||
* compile time. Having only 4 byte datums could make worst-case
|
* disabled at compile time. Having only 4 byte datums could make
|
||||||
* performance drastically more likely, for example. Moreover, macOS's
|
* worst-case performance drastically more likely, for example.
|
||||||
* strxfrm() implementation is known to not effectively concentrate a
|
* Moreover, macOS's strxfrm() implementation is known to not
|
||||||
* significant amount of entropy from the original string in earlier
|
* effectively concentrate a significant amount of entropy from the
|
||||||
* transformed blobs. It's possible that other supported platforms are
|
* original string in earlier transformed blobs. It's possible that
|
||||||
* similarly encumbered. So, if we ever get past disabling this
|
* other supported platforms are similarly encumbered. So, if we ever
|
||||||
* categorically, we may still want or need to disable it for particular
|
* get past disabling this categorically, we may still want or need to
|
||||||
* platforms.
|
* disable it for particular platforms.
|
||||||
*/
|
*/
|
||||||
if (!pg_strxfrm_enabled(locale))
|
if (!pg_strxfrm_enabled(locale))
|
||||||
abbreviate = false;
|
abbreviate = false;
|
||||||
|
|
Loading…
Reference in New Issue