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

Re: pg_migrator and an 8.3-compatible tsvector data type

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, 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 15:39:18
Message-ID: 1243611558.1301.43.camel@localhost (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane píše v pá 29. 05. 2009 v 11:28 -0400:
> Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> > 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.  
> No more than changing dictionary behavior in an existing installation.
> What was stated when the issue came up during 8.3 development is that
> you don't normally need to worry about small changes in dictionary
> behavior because overall text search behavior will still be "close
> enough".  (I seem to recall that I'd complained that any change in
> dictionary behavior would invalidate indexes based on the dictionary,
> and this was the answer.)

It seems to be OK then. However, pg_migrator should inform about it.


In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2009-05-29 15:42:09
Subject: Re: PostgreSQL Developer meeting minutes up
Previous:From: Tom LaneDate: 2009-05-29 15:38:16
Subject: Re: Python 3.0 does not work with PL/Python

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