From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Arturas Mazeika <mazeika(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5735: pg_upgrade thinks that it did not start the old server |
Date: | 2010-10-30 17:33:56 |
Message-ID: | AANLkTik3q_BbsOJOHcvzPuGa0AxMGbxaVrvJBpoLODwB@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sat, Oct 30, 2010 at 3:29 PM, Arturas Mazeika <mazeika(at)gmail(dot)com> wrote:
>
> -----------------------------
> Checking old data directory (I:\PostgreSQL\8.3\data) ok
> Checking old bin directory (C:\Program Files (x86)\PostgreSQL\8.3\bin)ok
> Checking new data directory (I:\PostgreSQL\9.0) 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.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-10-30 18:14:10 | Re: BUG #5732: parsing of: "WHERE mycol=123AND ..." |
Previous Message | Tom Lane | 2010-10-30 16:07:43 | Re: BUG #5734: autovacuum_enabled input should be validated, standardized. |