Re: Restoring a db dump with tsearch fields fails

From: "Thomas T(dot) Thai" <tom(at)minnesota(dot)com>
To: Robert John Shepherd <robert(at)reviewer(dot)co(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Restoring a db dump with tsearch fields fails
Date: 2002-11-08 01:42:13
Message-ID: Pine.NEB.4.43.0211071940390.17397-100000@ns01.minnesota.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Which version of pgsql? which version of tsearch?

I had similar problems and emailed the creators of tsearch and they
provided the fix. I believe it was later integrated back into the distro.

If you check the lines where those errors occur, I bet it is missing a
single or double quote around those word.

On Fri, 8 Nov 2002, Robert John Shepherd wrote:

> Bit of a problem here, am regularly backing up my database with
> pg_dumpall, which works fine.
>
> However when I attempt a restore on another box, things go rather
> pearshaped, and I'm pretty sure this is because I am using tsearch from
> the contrib directory.
>
> I've tried adding tsearch.sql to the template1 db, in case that helped,
> which it didn't. :/
>
> I get lots of these during the restore:
> ERROR: parser: parse error at or near "ikebe"
> ERROR: parser: parse error at or near "'"
> ERROR: parser: parse error at or near "ne"
> ERROR: parser: parse error at or near "'"
> ERROR: parser: parse error at or near "ad"
> ERROR: parser: parse error at or near "phane"
> ERROR: parser: parse error at or near "rgaard"
> ERROR: parser: parse error at or near "gnes"
> ERROR: parser: parse error at or near "e"
> ERROR: parser: parse error at or near "otis"
> ERROR: parser: parse error at or near "gis"
> ERROR: parser: parse error at or near "rald"
> Query buffer reset (cleared).
> invalid command \n
> Query buffer reset (cleared).
> invalid command \n<p
> Query buffer reset (cleared).
> invalid command \n<p
> Query buffer reset (cleared).
> invalid command \n<p
> Query buffer reset (cleared).
>
>
> I'm presuming all of these relate to the way pg_dump creates scripts for
> the tsearch fields.
>
> This could make restoring my database rather tricky if I ever have to do
> this for real. :o
>
> Anyone have any suggestions?
>
>
>
> Yours Unwhettedly,
> Robert John Shepherd.
>
> Editor
> DVD REVIEWER
> The UK's BIGGEST Online DVD Magazine
> http://www.dvd.reviewer.co.uk
>
> For a copy of my Public PGP key, email: pgp(at)robertsworld(dot)org(dot)uk
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>

--
Thomas T. Thai
Minnesota.com, Inc.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bill Gribble 2002-11-08 01:51:38 Re: [HACKERS] Database replication... - Mission Critica
Previous Message Christopher Kings-Lynne 2002-11-08 01:36:43 Re: [HACKERS] Database replication... - Mission Critica