Re: pg_migrator and an 8.3-compatible tsvector data type

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
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-29 13:27:34
Message-ID: 1243603654.1301.28.camel@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Bruce Momjian píše v čt 28. 05. 2009 v 17:42 -0400:
> Josh Berkus wrote:
> > On 5/28/09 2:30 PM, Bruce Momjian wrote:
> > > Because no one has responded, I am going to prevent pg_migrator from
> > > working with a cluster that uses tsvector. I realize this limits
> > > pg_migrator's usefulness, but I have to move on.
> >
> > I don't know how to fix the issue, certainly.
> >
> > Why was there a format change to tsvector anyway? Was there an
> > important reason for this?
>
> The ordering of the lexems was changed:

The biggest problem is dictionary change. I'm not sure if it happened
but IIRC Teodor mentioned it in Ottawa. If it happened It hits down
tsvector compatibility at all.

Zdenek

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-05-29 13:35:41 Re: PostgreSQL Developer meeting minutes up
Previous Message Stefan Kaltenbrunner 2009-05-29 12:58:45 Re: pg_migrator and an 8.3-compatible tsvector data type