Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UTDsh-0008Ci-CP for pgsql-admin@arkaria.postgresql.org; Fri, 19 Apr 2013 16:09:47 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1UTDsg-0004f1-91 for pgsql-admin@arkaria.postgresql.org; Fri, 19 Apr 2013 16:09:46 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UTDsf-0004ev-7r for pgsql-admin@postgresql.org; Fri, 19 Apr 2013 16:09:45 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1UTDsc-0007oC-Ja for pgsql-admin@postgresql.org; Fri, 19 Apr 2013 16:09:44 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r3JG9eHS017574; Fri, 19 Apr 2013 12:09:40 -0400 (EDT) From: Tom Lane To: Robert Treat cc: chanh.tran@free.fr, pgsql-admin@postgresql.org Subject: Re: Pb migrating database from Postgres 8.1 to 8.4 In-reply-to: References: <1513898572.54354333.1366376303229.JavaMail.root@spooler8-g27.priv.proxad.net> <15287.1366381161@sss.pgh.pa.us> Comments: In-reply-to Robert Treat message dated "Fri, 19 Apr 2013 11:34:10 -0400" Date: Fri, 19 Apr 2013 12:09:40 -0400 Message-ID: <17573.1366387780@sss.pgh.pa.us> X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Robert Treat writes: > On Fri, Apr 19, 2013 at 10:19 AM, Tom Lane wrote: >> chanh.tran@free.fr writes: >>> I'm facing pbs trying to migrate my current database from Postgres 8.1 to 8.4. >>> pg_restore: [archiver (db)] could not execute query: ERROR: could not find function "gtsvector_in" in file "/usr/lib64/pgsql/tsearch2.so" >> Looks like you're missing the shared library that underlies tsearch2. >> The other errors seem to be consequences of this one. > It might be cleaner to try and remove the tsearch bits from your > schema dump and get a fresh install of tsearch by itself before > loading in your own schema. Actually, on second look, I think this is expected behavior when trying to update from pre-8.3 text search --- that whole conversion was none too clean. Note the warning in the tsearch2 module documentation about 3. Load the dump data. There will be quite a few errors reported due to failure to recreate the original tsearch2 objects. These errors can be ignored, but this means you cannot restore the dump in a single transaction (eg, you cannot use pg_restore's -1 switch). If you weren't actually using the tsearch2 features before, you might be best advised to uninstall tsearch2 from the old database before you convert. If you were, please read the documentation about text search conversion carefully --- both http://www.postgresql.org/docs/8.4/static/textsearch-migration.html and the contrib/tsearch2 page. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin