]> granicus.if.org Git - postgresql/commit
Create an explicit concept of collations that work for any encoding.
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 11 Mar 2011 18:20:11 +0000 (13:20 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 11 Mar 2011 18:20:11 +0000 (13:20 -0500)
commite3c732a85c0f247617b2d44ea567f35731b03ea6
tree9693d47782b9f7431a56474e8c5b972d351bd4ec
parentac435a79c88f51be6bf3eb5df618c2bac6123ae4
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.
doc/src/sgml/catalogs.sgml
src/backend/catalog/information_schema.sql
src/backend/catalog/namespace.c
src/backend/catalog/pg_collation.c
src/backend/commands/collationcmds.c
src/bin/psql/tab-complete.c
src/include/catalog/catversion.h
src/include/catalog/pg_collation.h
src/test/regress/expected/collate.linux.utf8.out