Re: Restore from pg_dumpall - Mailing list pgsql-admin

From Buorn, Yoway
Subject Re: Restore from pg_dumpall
Date
Msg-id 21A801CCBAC79545878E3C1137912E410112D029@CAMV02-MAIL01.ad.gd-ais.com
Whole thread Raw
In response to Restore from pg_dumpall  ("Buorn, Yoway" <Yoway.Buorn@gd-ais.com>)
Responses Re: Restore from pg_dumpall
Re: Restore from pg_dumpall
List pgsql-admin
No, I'm not trying to back-port a dump.  I simply followed the
instructions in the section 2.3.4 of the gforge manual which tells me to
go into the db/ folder and apply the schema changes in order for all sql
files dated after the existing installation.  So I started with
20050312.sql and it gave me this parse error near "CASCADE".

You mention there's nothing wrong with this.  Does this mean the message
is not really an error and I can safely ignore it?

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, August 05, 2005 9:24 PM
To: Buorn, Yoway
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Restore from pg_dumpall

"Buorn, Yoway" <Yoway.Buorn@gd-ais.com> writes:
> I'm upgrading Gforge and the first sql file I tried to load gave me
> the = following error:

> DROP FUNCTION projtask_insert_depend () CASCADE ;
> ERROR:  parser: parse error at or near "CASCADE"

> Can anyone point out to me what is wrong with this sql?  Thanks.

Nothing ... in any PG version newer than 7.3 or so.  Are you trying to
back-port a dump into an older server version, and if so why?

            regards, tom lane

pgsql-admin by date:

Previous
From:
Date:
Subject:
Next
From: "Amrit Angsusingh"
Date:
Subject: DBmirror from 64 bit to 32 bit