Re: pg_trgm: unicode string not working - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_trgm: unicode string not working
Date
Msg-id 201106140211.p5E2BGc29320@momjian.us
Whole thread Raw
In response to Re: pg_trgm: unicode string not working  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas wrote:
> On Mon, Jun 13, 2011 at 7:47 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > Robert Haas wrote:
> >> On Sun, Jun 12, 2011 at 8:40 AM, Florian Pflug <fgp@phlo.org> wrote:
> >> > Note that this restriction was removed in postgres 9.1 which
> >> > is currently in beta. However, GIT indices must be re-created
> >> > with REINDEX after upgrading from 9.0 to leverage that
> >> > improvement.
> >>
> >> Does pg_upgrade know about this?
> >
> > No, it does not. ?Under what circumstances should I issue a suggestion
> > to reindex, and what should the text be?
> 
> It sounds like GIN indexes need to be reindexed after upgrading from <
> 9.1 to >= 9.1.

I already have some GIN tests I used for 8.3 to 8.4 so that is easy, but
is the reindex required or just suggested for features?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: lazy vxid locks, v1
Next
From: Bruce Momjian
Date:
Subject: Re: Creating new remote branch in git?