Re: GIN improvements part 1: additional information

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN improvements part 1: additional information
Date: 2013-10-03 21:24:49
Message-ID: 20131003212449.GA17613@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 3, 2013 at 02:48:20PM -0400, Robert Haas wrote:
> On Thu, Oct 3, 2013 at 2:43 PM, Heikki Linnakangas
> <hlinnakangas(at)vmware(dot)com> wrote:
> > It seems we've all but decided that we'll require reindexing GIN indexes in
> > 9.4.
>
> I thought the consensus in Ottawa was strongly against that. I'm not
> aware that anyone has subsequently changed their position on the
> topic. Bruce is right to point out that we've done such things before
> and can therefore do it again, but just because we have the technical
> means to do it doesn't make it good policy.
>
> That having been said, if we do decide to break it...

Agreed. I was stating only that this is easy for pg_upgrade. One cool
thing is that the upgrades completes, and the indexes are there, but
just marked as invalid until the REINDEX.

One other point Alexander made is that the new GIN indexes will be
smaller so most people would want the new format in the new cluster
anyway.

--
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-10-03 21:30:57 Re: GIN improvements part 1: additional information
Previous Message Alexander Korotkov 2013-10-03 20:54:31 Re: GIN improvements part 1: additional information