Re: WIP: store additional info in GIN index - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: WIP: store additional info in GIN index
Date
Msg-id 20121204203806.GG30893@momjian.us
Whole thread Raw
In response to Re: WIP: store additional info in GIN index  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Tue, Dec  4, 2012 at 05:35:24PM -0300, Alvaro Herrera wrote:
> > This means to have two versions of code which deals with posting trees and
> > lists. For me it seems unlikely we have resources for maintenance of this.
> 
> Witness how GIN has gone with unfixed bugs for months, even though
> patches to fix them have been posted.  We don't have the manpower to
> maintain even *one* such implementation, let alone two.
> 
> 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.

Yes, pg_upgrade has infrastructure to do that.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Commits 8de72b and 5457a1 (COPY FREEZE)
Next
From: Pavel Stehule
Date:
Subject: Re: review: Deparsing DDL command strings