Re: Need for re-index after pg_upgrade - Mailing list pgsql-general

From Andreas Joseph Krogh
Subject Re: Need for re-index after pg_upgrade
Date
Msg-id VisenaEmail.27.4df3a63e76297619.14e3f929e99@tc7-visena
Whole thread Raw
In response to Re: Need for re-index after pg_upgrade  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
På mandag 29. juni 2015 kl. 15:42:22, skrev Tom Lane <tgl@sss.pgh.pa.us>:
Andreas Joseph Krogh <andreas@visena.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?

regards, tom lane
 
I'm specifically thinking about this (from 9.4 release-notes):

E.5.3.1.1. Indexes

  • Reduce GIN index size (Alexander Korotkov, Heikki Linnakangas)

    Indexes upgraded via pg_upgrade will work fine but will still be in the old, larger GIN format. Use REINDEX to recreate old GIN indexes in the new format.

 
It'd be great if pg_upgrade generated re-index scripts to make those indexes use the new format.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
 
Attachment

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Need for re-index after pg_upgrade
Next
From: Adrian Klaver
Date:
Subject: Re: Need for re-index after pg_upgrade