| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| 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-13 23:47:31 |
| Message-ID: | 201106132347.p5DNlVp03226@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-06-14 00:05:55 | Why polecat and colugos are failing to build back branches |
| Previous Message | Josh Berkus | 2011-06-13 23:08:46 | Re: creating CHECK constraints as NOT VALID |