tsearch2 changes need backpatching? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject tsearch2 changes need backpatching?
Date
Msg-id 42BEB380.5050202@dunslane.net
Whole thread Raw
Responses Re: tsearch2 changes need backpatching?
Re: tsearch2 changes need backpatching?
List pgsql-hackers
The buildfarm member penguin (Debian, ARM) has been building the HEAD 
branch for the most part happily since late January, but keeps failing 
on the REL8_0_STABLE branch on tsearch2. It appears that some changes 
made around 24-27 January fixed it for this architecture/OS. Looking in 
the committers log, I see:


improve support of agglutinative languages (query with compound words)


and


Change
typedef struct {} WordEntryPos;
to
typedef uint16 WordEntryPos


Could one of these inadvertantly fix the problem we are seeing here? Do we need to backpatch to fix REL8_0_STABLE, or
applysome other fix?
 


cheers

andrew








pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fixing r-tree semantics
Next
From: Tom Lane
Date:
Subject: contrib/rtree_gist into core system?