| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Florian Pflug <fgp(at)phlo(dot)org>, sushant354(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_trgm: unicode string not working |
| Date: | 2011-06-14 01:58:57 |
| Message-ID: | BANLkTi=4YX6UsGQCR9s-88Qejtnskbsi6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 13, 2011 at 7:47 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Robert Haas wrote:
>> On Sun, Jun 12, 2011 at 8:40 AM, Florian Pflug <fgp(at)phlo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-06-14 02:01:28 | Re: creating CHECK constraints as NOT VALID |
| Previous Message | Robert Haas | 2011-06-14 01:57:49 | Re: Why polecat and colugos are failing to build back branches |