Re: rangetypes spgist questions/refactoring - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: rangetypes spgist questions/refactoring
Date
Msg-id 20140528104102.GB28490@momjian.us
Whole thread Raw
In response to Re: rangetypes spgist questions/refactoring  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Tue, May 20, 2014 at 11:18:29AM -0700, Jeff Davis wrote:
> I think this can be done without breaking upgrade compatibility, because
> I think the structure already satisfies the invariants I mentioned in
> the other email (aside from the special case of a root tuple with two
> nodes and no prefix). That being said, it's a little scary to refactor
> indexing code while trying to keep it upgrade-compatible.

We can make pg_upgrade mark such indexes as invalid and create a user
script to reindex all the indexes after the upgrade.  We have done
that in the past.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Race condition within _bt_findinsertloc()? (new page split code)
Next
From: David Rowley
Date:
Subject: Re: Allowing join removals for more join types