Re: pg_trgm: unicode string not working

From: Florian Pflug <fgp(at)phlo(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, sushant354(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_trgm: unicode string not working
Date: 2011-06-14 09:02:37
Message-ID: 3363CE45-F058-4EC3-A952-78E1C52B0826@phlo.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun14, 2011, at 07:15 , Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Mon, Jun 13, 2011 at 7:47 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>>> 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.
>
> Only if you care whether they work for corner cases such as empty
> arrays ... corner cases which didn't work before 9.1, so very likely
> you don't care.

We also already say "To fix this, do REINDEX INDEX ... " in the errhint
of "old GIN indexes do not support whole-index scans nor searches for nulls".

best regards,
Florian Pflug

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-06-14 09:40:32 Re: SSI patch renumbered existing 2PC resource managers??
Previous Message Shigeru Hanada 2011-06-14 08:56:05 per-column generic option