Re: pg 7.2.3 -> pg 7.3.3: pg_atoi error

From PostgreSQL changelog:
* An empty string ('') is no longer allowed as the input into an
   integer field. Formerly, it was silently interpreted as 0.
-  Disallow pg_atoi('') (Bruce)

----- Original Message -----
From: "Mark Stosberg" <mark@summersault.com>
To: <pgsql-novice@postgresql.org>
Sent: Saturday, August 02, 2003 4:39 AM
Subject: Re: [NOVICE] pg 7.2.3 -> pg 7.3.3: pg_atoi error


>
> > I get an pg_atoi error while reading in co_sys_meta_vtable,
> > I suppose at this
> >  "id" integer DEFAULT nextval('co_sys_meta_vtable_sqid'::text),
> > particular line.
>
> Could you post the exact error message you are getting?
>
> > Is there a way to successfully transport such a db into new version?
> > The dump has almost 3G, so hand-editing is not a case..
>
> Here are  some suggestions:
>
> 1. Try dumping and importing just the schema first. In my experience,
> most of the issues are in there when upgrading, and the files are much
> smaller.
>
> 2. If you suspect you know what change to make, you can use command line
> tools such as Perl to do a find and replace on the file. Here's an
> exapmle for Perl, which also creates a ".bak" file:
>
> perl -pi.bak -e 's/old/new/' schema.sql
>
> 3. Check the ChangeLogs between the versions in question to see if they
> provide a clue about what might have changed.
>
> 4. Some editors will handle huge files. I suspect vim will do fairly
> well. Other editors may be more tailored towards this application.
>
> I have an old document about upgrading Postgres. Some of the concepts
> may still apply:
>
> http://mark.stosberg.com/Tech/postgres/pg-65-7-upgrade.html
>
> Mark
>
> --
> http://mark.stosberg.com/
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings