tsearch2 changes need backpatching?

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: tsearch2 changes need backpatching?
Date: 2005-06-26 13:54:08
Message-ID: 42BEB380.5050202@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 apply some other fix?

cheers

andrew

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-06-26 14:03:46 contrib/rtree_gist into core system?
Previous Message Tom Lane 2005-06-26 13:52:03 Re: Fixing r-tree semantics