Mon Mar 9 08:26:56 PDT 2009
- Previous message: [Slony1-general] Multiple databases = multiple clusters?
- Next message: [Slony1-general] no timestamps in the slon logs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Karl Denninger <karl at denninger.net> writes: > The documentation has gotten me through replicating one database. > > Ok, I now I have another one on the same machine going to the same > destination. Its a different database with obviously different tables. > > Am I correct that I need only one "slon" process per computer (or > Postgresql instance) but that when I set up other replication sets > for different databases I set them up as different clusters? You need one "slon" for each PostgreSQL database that is participating in replication. The edge case here would be that if a particular PostgreSQL cluster (e.g. - an instance running on a particular host responding at a particular port) has *two* databases involved in replication, then *two* slons would be required, one for each database. But if you have several replication sets that aren't particularly similar to one another, that don't really need to interact, I'd expect it to be wise to set them up as completely separate Slony-I clusters. -- "cbbrowne","@","linuxdatabases.info" http://cbbrowne.com/info/unix.html "...In my phone conversation with Microsoft's lawyer I copped to the fact that just maybe his client might see me as having been in the past just a bit critical of their products and business practices. This was too bad, he said with a sigh, because they were having a very hard time finding a reporter who both knew the industry well enough to be called an expert and who hadn't written a negative article about Microsoft." -- Robert X. Cringely
- Previous message: [Slony1-general] Multiple databases = multiple clusters?
- Next message: [Slony1-general] no timestamps in the slon logs
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list