| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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 22:47:07 |
| Message-ID: | 20121204224707.GH30893@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 4, 2012 at 05:35:27PM -0500, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > 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.
>
> Bumping the version number in the GIN metapage would be sufficient.
And it is easy for pg_upgrade to report which indexes need rebuilding,
and it can create a script file to do the reindexing.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-12-04 22:48:37 | Re: PITR potentially broken in 9.2 |
| Previous Message | Tom Lane | 2012-12-04 22:35:27 | Re: WIP: store additional info in GIN index |