Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try
Date: 2009-03-24 21:16:04
Message-ID: 8662.1237929364@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> 2009/3/24 Tom Lane <tgl(at)postgresql(dot)org>:
>> catversion bumped because of change in GIN's pg_am entry, and because
>> the format of GIN indexes changed on-disk (there's a metapage now,
>> and possibly a pending list).

> Will this break pg_migrator?

No worse than it's already broken by hash indexes. I would imagine
the strategy will just be to force a REINDEX on any non-btree indexes.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message User Hinoue 2009-03-24 21:38:46 psqlodbc - psqlodbc: Add a textbox to setup dialog to change the
Previous Message Tom Lane 2009-03-24 21:12:56 pgsql: Fix stupid parenthesization mistake.

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Lor 2009-03-24 21:31:43 Re: DTrace probes broken in HEAD on Solaris?
Previous Message Robert Haas 2009-03-24 20:52:22 Re: [COMMITTERS] pgsql: Implement "fastupdate" support for GIN indexes, in which we try