Wed Jun 11 10:51:12 PDT 2008
- Previous message: [Slony1-general] Re: Newbie to slony-1
- Next message: [Slony1-general] replication set up, but no replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm am totally confused and really don't know where else to look. We have 12 databases that I'm trying to replicate. They all have their own postmaster and separate ports. I wrote a script, which uses the altperl scripts to setup slony and get replication going. This script has worked flawlessly in the past. All you do is pass it the database name and it takes it from there. I put it in a loop so that it would run through all the databases. Now here's the weird part. Although it appears that all databases were properly set up for replication, about half of them are not. That is to say, that tables that I know should be replicating have no records in them on the node 2 box. So, I started over and first tested one of the databases that properly replicated and it worked fine again. I then ran the same script for one of the databases that did not replicate, and again there is no transfer of data. The tables are empty on the node 2 machine. Looking at the logs, I don't see anything that jumps out at me. How can I determine why this is not working? Both machines are running Red Hat EL 4 and: Postgres 8.3.1 slony 1.2.14 -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
- Previous message: [Slony1-general] Re: Newbie to slony-1
- Next message: [Slony1-general] replication set up, but no replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list