My problem seems to be solved. Actually it was because of the differences between the version of pg_dump/pg_restore (8.3) and of my postgres DB (8.2.6). As i used the appropriate versions for pg_dump/pg_restore the restauration runs through without any errors. Thanks for that Andreas Actually i used version 8.2.6 both for pg_restore and pg_dump. On Tue, Feb 26, 2008 at 10:48:06AM +0100, Andreas Lau wrote: > Thanks for your hinds. > It's true i used pg_dump and pg_restore version 8.3 to dump and restore 8.2 databases. I wouldn't have thought that there could be problems. But it seems so. I will give it a try an report the result. > > Thanks Andreas > > -----Ursprüngliche Nachricht----- > Von: Magnus Hagander [mailto:magnus@xxxxxxxxxxxx] > Gesendet: Dienstag, 26. Februar 2008 10:30 > An: Andreas Lau; pgsql-general@xxxxxxxxxxxxxx > Betreff: Re: syntax error at or near "PROCEDURAL" > > On Tue, Feb 26, 2008 at 10:26:25AM +0100, Martijn van Oosterhout wrote: > > On Tue, Feb 26, 2008 at 10:23:05AM +0100, Magnus Hagander wrote: > > > Any chance you are running pg_dump/pg_restore version 8.3? The > > > syntax appears to be what 8.3 uses, not 8.3.. > > > > > > You can use (and should use) an 8.3 pg_dump to dump your 8.2 > > > database when upgrading to 8.3, but you often can't reload a dump > > > created by 8.3 on an > > > 8.3 database. > > > > I think some of those 3's need to be 2's... > > Argh. Yes. The last one in each paragraph. I blame fosdem-recovery ;-) > > //Magnus ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
