pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
To: Elliot Voris <evoris@slcconline.edu>
Subject: Re: Importing SQL file into PostgreSQL database
Date: Wed, 13 Jul 2011 14:49:46 -0500
Message-ID: <4E1DB08A020000250003F2B7@gw.wicourts.gov> (raw)
In-Reply-To: <0FB9449006048B4AA23E50C90C1B9209055DD3EE@CH1PRD0202MB157.namprd02.prod.outlook.com>
References: <0FB9449006048B4AA23E50C90C1B9209055DD3EE@CH1PRD0202MB157.namprd02.prod.outlook.com>

Elliot Voris <evoris@slcconline.edu> wrote:
> I work for a small college, where the library uses Evergreen to
> manage it's collection. The database is PostgreSQL driven. The
> server that Evergreen was running on crashed. The old server was
> running PostgreSQL 8.3. I've installed an updated version of
> Evergreen, including PostgreSQL 8.4.8.
 
Did that come as part of the Evergreen install package?  If not, did
Evergreen provide any advice on what to download or install?
 
> I have a backup of the database in a SQL file.
 
Made with the old version of PostgreSQL against the old version of
the Evergreen database?
 
> When I try to import the file into the new 
> database I get the following output:
> 
> postgres@server:~$ psql database < olddb.sql
> SET
> SET
> SET
> SET
> SET
> SET
> setval
> --------
>   23405
> (1 row)
> 
> ERROR:  function xml_is_well_formed(text) does not exist
> LINE 1: SELECT xml_is_well_formed( $1 )
 
I would double-check what the supported method of upgrading
Evergreen is.  FWIW, it is generally much better to dump a
PostgreSQL database with the version of pg_dump matching the
database into which it will be *restored* rather than matching the
database version being dumped.  That can be worked around, but your
first concern should probably be whether the new version of the
Evergreen software will work with a copy of the database from the
old version.  You might be best served by installed the old version,
from which you have a dump, and then following the standard upgrade
procedure for Evergreen -- rather than trying to take any short
cuts.
 
Whatever you do, protect that dump until well after you have things
running smoothly.
 
-Kevin



view thread (2+ messages)

Message-ID: <4E1DB08A020000250003F2B7@gw.wicourts.gov>
Permalink:  ../4E1DB08A020000250003F2B7@gw.wicourts.gov/
Also on:    postgresql.org/message-id/4E1DB08A020000250003F2B7@gw.wicourts.gov

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: Kevin.Grittner@wicourts.gov, evoris@slcconline.edu
  Subject: Re: Importing SQL file into PostgreSQL database
  In-Reply-To: <4E1DB08A020000250003F2B7@gw.wicourts.gov>
  References: <0FB9449006048B4AA23E50C90C1B9209055DD3EE@CH1PRD0202MB157.namprd02.prod.outlook.com> <4E1DB08A020000250003F2B7@gw.wicourts.gov>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox