Maintain row-security status properly in cached plans (Stephen Frost) C locale is known safe, and there is no evidence of trouble in English-based locales such as en_US, but some other popular locales such as de_DE are affected in most glibc versions. It is not possible at this time to give an exhaustive list of known-affected locales. Users should REINDEX indexes that might be affected. Unfortunately, this problem affects not only sorting but also entry ordering in B-tree indexes, which means that B-tree indexes on text, varchar, or char columns may now be corrupt if they sort according to an affected locale and were built or modified under PostgreSQL 9.5.0 or 9.5.1. (C locale is safe since it uses neither strcoll() nor strxfrm().) Until this problem can be better characterized, disable the optimization in all non-C locales. It now emerges that most versions of glibc (Linux's implementation of the C library) have buggy implementations of strxfrm() that, in some locales, can produce string comparison results that do not match strcoll(). PostgreSQL 9.5 introduced logic for speeding up comparisons of string data types by using the standard C library function strxfrm() as a substitute for strcoll(). Disable abbreviated keys for string sorting in non-C locales (Robert Haas) However, you may need to REINDEX some indexes after applying the update, as per the first changelog entry below. A dump/restore is not required for those running 9.5.X.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |