Re: 8.2.6 > 8.3 blows up

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Karl Denninger <karl(at)denninger(dot)net>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: 8.2.6 > 8.3 blows up
Date: 2008-03-02 23:22:24
Message-ID: 25078.1204500144@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Karl Denninger <karl(at)denninger(dot)net> writes:
> It looks like the problem had to do with the tsearch2 module that I have
> in use in a number of my databases, and which had propagated into
> template1, which meant that new creates had it in there.

The old tsearch2 module isn't at all compatible with 8.3. I'd suggest
removing it from the 8.2 source databases where possible, ie wherever
you're not actually using it. Where you are using it, the cure is to
install the 8.3 version of contrib/tsearch2 into the target database
*before* restoring. See
http://www.postgresql.org/docs/8.3/static/textsearch-migration.html
http://www.postgresql.org/docs/8.3/static/tsearch2.html

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karl Denninger 2008-03-02 23:28:57 Re: 8.2.6 > 8.3 blows up
Previous Message Karl Denninger 2008-03-02 23:20:30 Re: 8.2.6 > 8.3 blows up