Horton
Menu

Re: WIP: store additional info in GIN index

Bruce Momjian <bruce@momjian.us>

View thread
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Alexander Korotkov <aekorotkov@gmail.com>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-12-04T22:47:07Z
Lists: pgsql-hackers 
On Tue, Dec  4, 2012 at 05:35:27PM -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > Maybe we can mark GIN indexes as invalid after pg_upgrade somehow, so
> > that they require reindex in the new cluster before they can be used for
> > queries or index updates.
> 
> Bumping the version number in the GIN metapage would be sufficient.

And it is easy for pg_upgrade to report which indexes need rebuilding,
and it can create a script file to do the reindexing.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +