From bb850306307d3d6ebb611c4039ae127236eb1699 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 22 Apr 2011 20:19:58 -0400 Subject: Fix contrib/btree_gist to handle collations properly. Make use of the collation attached to the index column, instead of hard-wiring DEFAULT_COLLATION_OID. (Note: in theory this could require reindexing btree_gist indexes on textual columns, but I rather doubt anyone has one with a non-default declared collation as yet.) --- contrib/btree_gist/btree_utils_num.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'contrib/btree_gist/btree_utils_num.c') diff --git a/contrib/btree_gist/btree_utils_num.c b/contrib/btree_gist/btree_utils_num.c index 64c95854df8..a3da5802df2 100644 --- a/contrib/btree_gist/btree_utils_num.c +++ b/contrib/btree_gist/btree_utils_num.c @@ -184,9 +184,11 @@ gbt_num_bin_union(Datum *u, GBT_NUMKEY *e, const gbtree_ninfo *tinfo) /* -** The GiST consistent method -*/ - + * The GiST consistent method + * + * Note: we currently assume that no datatypes that use this routine are + * collation-aware; so we don't bother passing collation through. + */ bool gbt_num_consistent(const GBT_NUMKEY_R *key, const void *query, -- cgit v1.2.3