From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Arturas Mazeika <mazeika(at)gmail(dot)com> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5735: pg_upgrade thinks that it did not start the old server |
Date: | 2010-11-08 21:23:38 |
Message-ID: | AANLkTimO3MW9sTWR5yo5oRz+gBXqyHMn=yt6y4WJ3JtP@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Sat, Oct 30, 2010 at 9:30 PM, Arturas Mazeika <mazeika(at)gmail(dot)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 (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 migrate
> 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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Arturas Mazeika | 2010-11-09 09:45:49 | Re: BUG #5735: pg_upgrade thinks that it did not start the old server |
Previous Message | Robert Haas | 2010-11-07 01:28:35 | Re: BUG #5742: cannot alter column |