Arturas Mazeika wrote:
> Hi Dave,
>
> 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?
>
> Thanks,
> arturas
>
> On 10/30/2010 7:33 PM, Dave Page wrote:
> > 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.
Can anyone suggest a way pg_upgrade could detect an upgrade from a
32-bit to 64-bit cpu and throw an error?
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
