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

From Robert Haas
Subject Re: pg_trgm: unicode string not working
Date
Msg-id BANLkTi=4YX6UsGQCR9s-88Qejtnskbsi6g@mail.gmail.com
Whole thread Raw
In response to Re: pg_trgm: unicode string not working  (Bruce Momjian <bruce@momjian.us>)
Responses Re: pg_trgm: unicode string not working
Re: pg_trgm: unicode string not working
List pgsql-hackers
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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Why polecat and colugos are failing to build back branches
Next
From: Robert Haas
Date:
Subject: Re: creating CHECK constraints as NOT VALID