From rob at eorbit.net  Wed Nov 28 22:10:20 2007
From: rob at eorbit.net (Robert Kaye)
Date: Wed Nov 28 22:10:23 2007
Subject: [mb-datafeed] IMPORTANT: Clients using Postgres 8.0.x need to
	upgrade to Postgres 8.1.x
Message-ID: <4E0C9D8B-6B15-466C-8F15-94B1063535C2@eorbit.net>

Hi!

The main server, running postgres 8.1, emitted a replication packet  
that contains a UNICODE character that clients using postgres 8.0  
cannot process. In order to continue the replication stream, you must  
upgrade your postgres installation to 8.1.

To upgrade Postgres, download the 8.1.10 tarball and read INSTALL. In  
the INSTALL file is a section that contains detailed instructions on  
how to upgrade an existing postgres installation. Follow those  
instructions and empty the "Pending" and "PendingData" tables (see  
step 9) should be all that is required to upgrade your installation.

In order to upgrade one client that I have access to, I did:

0. Download and compile a new postgres installation.

1. Disable cron jobs.

2. Using the *OLD* postgres installation, dump all the tables with:

     pg_dumpall -h localhost -U postgres > /tmp/postgres-8.0.dumpall

3. Stop the old postgres instance

4. Install the new postgres version. I installed mine into a directory  
parallel to the old installation and used an entirely new database  
data directory.

5. copy configuration settings from my old postgres install  
(postgres.conf, pg_hba.conf) to the new postgres install.

6. Create a new postgres data directory using initdb as specified in  
INSTALL. Remember to specify the locale=C argument to initdb

7. Start new instance of postgres.

8. Import the data from the old postgres using the *NEW* postgres  
installation:

     psql -d postgres -U postgres -f /tmp/postgres-8.0.7.dumpall

9. Empty the "Pending" and "PendingData" tables.

     cd mb_server/admin
     ./psql READWRITE
     delete from "Pending";
     delete from "PendingData";

10. Catch up replication packets and make sure all is well

     cd mb-server/admin/replication
     ./LoadReplicationChanges

11. Re enable cron jobs.

That should be it. Sorry for the inconvenience!

--

--ruaok      Somewhere in Texas a village is *still* missing its idiot.

Robert Kaye     --     rob@eorbit.net     --    http://mayhem-chaos.net