Re: 7.2.2 upgrade, pg_dumpall / reload problem

On 10/9/02 4:02 pm, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 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

Yes, I discovered that when I restarted the server after I 'upgraded' I was
still running 7.2!! problem is with the installer package I downloaded it is
impossible to tell what it actually did! Anyway, scrapped that idea and have
just installed 7.2.2 using fink and all is fine

Thanks

Adam