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

Re: pg_migrator and an 8.3-compatible tsvector data type

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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:26:52
Message-ID: 200905282226.n4SMQq528296@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane wrote:
> 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 ;-)

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(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

Responses

pgsql-hackers by date

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

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