Re: pg_migrator and an 8.3-compatible tsvector data type - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_migrator and an 8.3-compatible tsvector data type
Date
Msg-id 200905282226.n4SMQq528296@momjian.us
Whole thread Raw
In response to Re: pg_migrator and an 8.3-compatible tsvector data type  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_migrator and an 8.3-compatible tsvector data type  (Greg Stark <stark@enterprisedb.com>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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 ;-)

Kind of --- I am stuck because we don't auto-cast for index usage like
we do for function calls and operators, so I will just keep going and
disable tsvector.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pg_migrator and an 8.3-compatible tsvector data type
Next
From: Tom Lane
Date:
Subject: Re: Dtrace probes documentation