0001-Fix-one-more-locale-operation-to-be-invoked-but-no-c.patch
text/x-patch
Filename: 0001-Fix-one-more-locale-operation-to-be-invoked-but-no-c.patch
Type: text/x-patch
Part: 0
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: format-patch
Series: patch 0001
Subject: Fix one more 'locale operation to be invoked, but no collation was derived' error
| File | + | − |
|---|---|---|
| src/backend/access/index/indexam.c | 1 | 1 |
From 91cf261c2af263e0965f5b302129730a7530ff38 Mon Sep 17 00:00:00 2001 From: Andres Freund <andres@anarazel.de> Date: Sat, 5 Mar 2011 23:45:22 +0100 Subject: [PATCH] Fix one more 'locale operation to be invoked, but no collation was derived' error The error was caused by directly accessing Relation.rd_index.indcollation. The latter is positioned after a variable length field and thus cannot be accessed directly. Instead use Relation.indcollation which is provided for that purpose. --- src/backend/access/index/indexam.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/backend/access/index/indexam.c b/src/backend/access/index/indexam.c index 6e6af18..f489400 100644 --- a/src/backend/access/index/indexam.c +++ b/src/backend/access/index/indexam.c @@ -872,7 +872,7 @@ index_getprocinfo(Relation irel, procnum, attnum, RelationGetRelationName(irel)); fmgr_info_cxt(procId, locinfo, irel->rd_indexcxt); - fmgr_info_collation(irel->rd_index->indcollation.values[attnum-1], + fmgr_info_collation(irel->rd_indcollation[attnum-1], locinfo); } -- 1.7.1