Re: GIN improvements part 1: additional information - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: GIN improvements part 1: additional information
Date
Msg-id 20131003213102.GU5235@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: GIN improvements part 1: additional information  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian escribió:

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

But they're nonfunctional until after the reindex, which is bad for
people who want a quick upgrade and return to operational mode
immediately.  If you could just keep the old indexes around, in working
state, until they are REINDEX CONCURRENTLY'ed, that would be more
practical than just marking them invalid.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: GIN improvements part 1: additional information
Next
From: Sergey Konoplev
Date:
Subject: Any reasons to not move pgstattuple to core?