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

From Robert Haas
Subject Re: BUG #5735: pg_upgrade thinks that it did not start the old server
Date
Msg-id AANLkTimO3MW9sTWR5yo5oRz+gBXqyHMn=yt6y4WJ3JtP@mail.gmail.com
Whole thread Raw
In response to Re: 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
Re: BUG #5735: pg_upgrade thinks that it did not start the old server
List pgsql-bugs
On Sat, Oct 30, 2010 at 9:30 PM, Arturas Mazeika <mazeika@gmail.com> wrote:
> Thanks for the info, this explains a lot.
>
> Yes, I am upgrading from the 32bit version to the 64bit one.
>
> We have pretty large databases =A0(some over 1 trillion of rows, and some
> containing large documents in blobs.) Giving a bit more memory than 4GB
> limit to Postgres was what we were long longing for. Postgres was able to
> handle large datasets (I suppose it uses something like long long (64bit)
> data type in C++) and I hoped naively that Postgres would be able to migr=
ate
> from one version to the other without too much trouble.
>
> I tried to pg_dump one of the DBs with large documents. I failed with out=
 of
> memory error. I suppose it is rather hard to migrate in my case :-( Any
> suggestions?

Yikes, that's not good.  How many tables do you have in your database?
 How many large objects?  Any chance you can coax a stack trace out of
pg_dump?

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-bugs by date:

Previous
From: "Matas"
Date:
Subject: BUG #5744: Debugging doesn't work in version 8.3.12 on windows.
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: BUG #5735: pg_upgrade thinks that it did not start the old server