-
- Downloads
Create an explicit concept of collations that work for any encoding.
Use collencoding = -1 to represent such a collation in pg_collation. We need this to make the "default" entry work sanely, and a later patch will fix the C/POSIX entries to be represented this way instead of duplicating them across all encodings. All lookup operations now search first for an entry that's database-encoding-specific, and then for the same name with collencoding = -1. Also some incidental code cleanup in collationcmds.c and pg_collation.c.
Showing
- doc/src/sgml/catalogs.sgml 7 additions, 5 deletionsdoc/src/sgml/catalogs.sgml
- src/backend/catalog/information_schema.sql 3 additions, 3 deletionssrc/backend/catalog/information_schema.sql
- src/backend/catalog/namespace.c 35 additions, 13 deletionssrc/backend/catalog/namespace.c
- src/backend/catalog/pg_collation.c 41 additions, 26 deletionssrc/backend/catalog/pg_collation.c
- src/backend/commands/collationcmds.c 59 additions, 24 deletionssrc/backend/commands/collationcmds.c
- src/bin/psql/tab-complete.c 1 addition, 1 deletionsrc/bin/psql/tab-complete.c
- src/include/catalog/catversion.h 1 addition, 1 deletionsrc/include/catalog/catversion.h
- src/include/catalog/pg_collation.h 5 additions, 5 deletionssrc/include/catalog/pg_collation.h
- src/test/regress/expected/collate.linux.utf8.out 6 additions, 6 deletionssrc/test/regress/expected/collate.linux.utf8.out
Loading
Please register or sign in to comment