Re: 7.2.2 upgrade, pg_dumpall / reload problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Adam Witney <awitney(at)sghms(dot)ac(dot)uk>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: 7.2.2 upgrade, pg_dumpall / reload problem
Date: 2002-09-10 15:02:53
Message-ID: 19614.1031670173@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Adam Witney <awitney(at)sghms(dot)ac(dot)uk> writes:
> I just upgraded from 7.2 to 7.2.2 using Mark Liyanage's prebuilt MacOSX 10.2
> package
> ...
> FATAL 1: Database "bugasbase" does not exist in the system catalog.
> psql:/tmp/postgresql.dump:21: \connect: FATAL 1: Database "bugasbase" does
> not exist in the system catalog.

> I have a database called BugasBase.... However this seems to be trying to
> find bugasbase

Yeah. This is a problem in the 7.2 pg_dumpall: it's careless about quoting
database names. You'll need to hand-edit the dump script to fix it.

(But hmm ... actually I thought the fix for that issue was a band-aid
patch in psql. Are you sure you are invoking the 7.2.2 psql, and not
a 7.2 copy?)

There wasn't any reason to do a dump and restore for a 7.2 to 7.2.2
upgrade anyway, so if you haven't blown away your old $PGDATA directory
yet, I'd counsel just forgetting the dump and starting your new
postmaster in the old data directory. A dump made with 7.2.2's pg_dump
should work okay.

regards, tom lane

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Bruce Momjian 2002-09-10 15:40:24 Re: fsync or fdatasync
Previous Message Alex Ott 2002-09-10 09:21:35 how can i get free space for database?