Re: Need for re-index after pg_upgrade

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andreas Joseph Krogh <andreas(at)visena(dot)com>
Cc: pgsql-general(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: Need for re-index after pg_upgrade
Date: 2015-06-29 13:58:50
Message-ID: 55914F1A.303@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 06/29/2015 06:42 AM, Tom Lane wrote:
> Andreas Joseph Krogh <andreas(at)visena(dot)com> writes:
>> In the man-page for pg_upgrade we see this:
>> pg_upgrade will require a reindex if:
>> * an index is of type hash or GIN
>
> I think that probably refers to some version-specific upgrade
> situations; I can't see a reason why it would be true in general.
> Bruce, doesn't that doc need improvement?

Yes for coming from 8.3:

http://www.postgresql.org/docs/9.4/static/pgupgrade.html

Limitations in Upgrading from PostgreSQL 8.3
....

pg_upgrade will require a reindex if:

an index is of type hash or GIN

an index uses bpchar_pattern_ops

This how it shows up my 9.4 man file also.

>
> regards, tom lane
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Merlin Moncure 2015-06-29 14:49:26 Re: Correct place for feature requests
Previous Message Andreas Joseph Krogh 2015-06-29 13:49:30 Re: Need for re-index after pg_upgrade