From 7208fae18f1fdb242b4fcced77a3b836e15ac3ec Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sat, 26 Mar 2011 18:28:40 -0400 Subject: Clean up cruft around collation initialization for tupdescs and scankeys. I found actual bugs in GiST and plpgsql; the rest of this is cosmetic but meant to decrease the odds of future bugs of omission. --- src/backend/access/gin/ginutil.c | 2 ++ 1 file changed, 2 insertions(+) (limited to 'src/backend/access/gin/ginutil.c') diff --git a/src/backend/access/gin/ginutil.c b/src/backend/access/gin/ginutil.c index 23965449df2..9c4473c449b 100644 --- a/src/backend/access/gin/ginutil.c +++ b/src/backend/access/gin/ginutil.c @@ -56,6 +56,8 @@ initGinState(GinState *state, Relation index) origTupdesc->attrs[i]->atttypid, origTupdesc->attrs[i]->atttypmod, origTupdesc->attrs[i]->attndims); + TupleDescInitEntryCollation(state->tupdesc[i], (AttrNumber) 2, + origTupdesc->attrs[i]->attcollation); } fmgr_info_copy(&(state->compareFn[i]), -- cgit v1.2.3