Skip site navigation (1) Skip section navigation (2)

Re: pg_migrator and an 8.3-compatible tsvector data type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Teodor Sigaev <teodor(at)sigaev(dot)ru>
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Date: 2009-05-28 22:19:01
Message-ID: 1666.1243549141@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Josh Berkus wrote:
>> Given that it's going to prevent users of Tsearch from 
>> upgrading-in-place, the format change ought to be giving us some serious 
>> gains.  Otherwise we should put it off until we need to make other 
>> datatype changes.

> No idea but now that we are in beta we would then be invalidating beta
> tester data.  The area I got stuck on is that there is no CAST behavior
> when creating an index.  We are already invalidating GIN indexes, but I
> can't even create an index to support the old data type.

It's certainly doable.  Bruce is just applying the strategy he mentioned
in our talk ;-)

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Josh BerkusDate: 2009-05-28 22:20:11
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Previous:From: Tom LaneDate: 2009-05-28 22:16:56
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group