aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2011-04-09 16:24:36 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2011-04-09 16:24:36 -0400
commitf89e4dfa755b9c9be9c19f7c65cff50d47b4f33a (patch)
tree444edb6c655185bbd234021e4b56dc49238a15a1 /src/backend/access/gist/gistproc.c
parenta19002d4e5da028ff7280554b281e402c609898b (diff)
downloadpostgresql-f89e4dfa755b9c9be9c19f7c65cff50d47b4f33a.tar.gz
postgresql-f89e4dfa755b9c9be9c19f7c65cff50d47b4f33a.zip
Remove collate.linux.utf8.sql's assumptions about ".utf8" in locale names.
Tweak the test so that it does not depend on the platform using ".utf8" as the extension signifying that a locale uses UTF8 encoding. For the most part this just requires using the abbreviated collation names "en_US" etc, though I had to work a bit harder on the collation creation tests. This opens the door to using the test on platforms that spell locales differently, for example ".utf-8" or ".UTF-8". Also, the test is now somewhat useful with server encodings other than UTF8; though depending on which encoding is selected, different subsets of it will fail for lack of character set support.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions