Re: BUG #5735: pg_upgrade thinks that it did not start the old server - Mailing list pgsql-bugs

From Dave Page
Subject Re: BUG #5735: pg_upgrade thinks that it did not start the old server
Date
Msg-id AANLkTik3q_BbsOJOHcvzPuGa0AxMGbxaVrvJBpoLODwB@mail.gmail.com
Whole thread Raw
In response to BUG #5735: pg_upgrade thinks that it did not start the old server  ("Arturas Mazeika" <mazeika@gmail.com>)
Responses Re: BUG #5735: pg_upgrade thinks that it did not start the old server  (Arturas Mazeika <mazeika@gmail.com>)
List pgsql-bugs
On Sat, Oct 30, 2010 at 3:29 PM, Arturas Mazeika <mazeika@gmail.com> wrote:
>
> -----------------------------
> Checking old data directory (I:\PostgreSQL\8.3\data) =A0 =A0 =A0 =A0ok
> Checking old bin directory (C:\Program Files (x86)\PostgreSQL\8.3\bin)ok
> Checking new data directory (I:\PostgreSQL\9.0) =A0 =A0 =A0 =A0 =A0 =A0 ok
> Checking new bin directory (C:\Program Files\PostgreSQL\9.0\bin)ok

I can't comment on the problem reported as I'm not that familiar with
pg_upgrade, but from the paths above, it looks like you're trying to
upgrade from a 32bit 8.3 server to a 64 bit 9.0 server, which isn't
going to work without a dump/restore. With pg_upgrade, the two builds
need to be from the same platform, same word size, and have the same
configuration for certain settings like integer_datetimes.


--=20
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: "Arturas Mazeika"
Date:
Subject: BUG #5735: pg_upgrade thinks that it did not start the old server
Next
From: Greg Stark
Date:
Subject: Re: BUG #5732: parsing of: "WHERE mycol=123AND ..."