mirrors
/
postgres
mirror of https://github.com/postgres/postgres
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix pgindent damage 

Oversight in commit a95ff1fe2e
This commit is contained in:
Robert Haas 2024-08-21 09:58:11 -04:00
parent 4baff50132
commit 2b03cfeea4
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
src/backend/utils/adt/varlena.c
View File

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