Thread: Looking for professionals for a PG server move
From 8.2.9 on a 32 bit Linux CentOS server to a different server (Cpanel/WHM) which is now running 8.4.2 with 64 bit CentOS. Truly appreciate any pointers or recommendations of good folks who can do this, or have done this. Thanks!
On 01/01/2010 02:01 AM, Phoenix Kiula wrote: > From 8.2.9 on a 32 bit Linux CentOS server to a different server > (Cpanel/WHM) which is now running 8.4.2 with 64 bit CentOS. > > Truly appreciate any pointers or recommendations of good folks who can > do this, or have done this. > > Thanks! > Ahh? Above a backup and restore? Like Absolutely no down time? Or its a 50 Terabyte database? Or both? What problemsare you having? On the new box, pg_dump the database from the old box, then restore it on the new. Did you try this? -Andy
Andy Biggest problem is utf-8 crap. Some other databases are much more forgiving of the data. PG takes utf-8 data but somehow gives problem with backup/restore. I've tried everything, including iconv etc, but this truly could be a lot better in the future versions I hope. Thanks. On Sat, Jan 2, 2010 at 12:06 AM, Andy Colson <andy@squeakycode.net> wrote: > On 01/01/2010 02:01 AM, Phoenix Kiula wrote: >> >> From 8.2.9 on a 32 bit Linux CentOS server to a different server >> (Cpanel/WHM) which is now running 8.4.2 with 64 bit CentOS. >> >> Truly appreciate any pointers or recommendations of good folks who can >> do this, or have done this. >> >> Thanks! >> > > Ahh? Above a backup and restore? Like Absolutely no down time? Or its a 50 > Terabyte database? Or both? What problems are you having? > > On the new box, pg_dump the database from the old box, then restore it on > the new. Did you try this? > > -Andy >
Phoenix Kiula <phoenix.kiula@gmail.com> writes:
> Biggest problem is utf-8 crap. Some other databases are much more
> forgiving of the data. PG takes utf-8 data but somehow gives problem
> with backup/restore. I've tried everything, including iconv etc, but
> this truly could be a lot better in the future versions I hope.
If you want "forgiving", maybe you should run your database in SQL_ASCII
mode.
regards, tom lane