Re: WIP: store additional info in GIN index

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: store additional info in GIN index
Date: 2012-12-04 20:38:06
Message-ID: 20121204203806.GG30893@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2012-12-04 20:46:11 Re: review: Deparsing DDL command strings
Previous Message Jeff Davis 2012-12-04 20:38:00 Re: Commits 8de72b and 5457a1 (COPY FREEZE)