James Tucker wrote:
James, thanks for you response, this is likely the path I'll choose as well.

Hi Geoffrey,

I've seen a few responses however not sure that your question has been
answered.  We run a similar configuration, about 10 separate databases all
replicated to a corresponding slave in the DR site.  You need to run a slon
daemon for each node in each cluster, so you'll end up with a lot of slony
processes.  I just created a different .conf file for each db and then to
control them, call them individually using the slon_start script.

i.e.

DB1 = /usr/local/slony/db1/db1.conf
DB2 = /usr/local/slony/db2/db2.conf

start db1 node 1.
slon_start --config /usr/local/slony/db1/db1.conf 1

start db2 node 1
slon_start --config /usr/local/slony/db2/db2.conf 1

I also use different users for each database to give some separation.  I've
noticed the slon_kill script will kill all the watchdog processes for all
db's if they run as the same user which is another good reason to separate.

Cheers

James


On Dec 22, 2007 6:00 AM, <[EMAIL PROTECTED]> wrote:

----------------------------------------------------------------------

Message: 1
Date: Fri, 21 Dec 2007 07:39:27 -0500
From: Geoffrey <[EMAIL PROTECTED]>
Subject: [Slony1-general] multiple databases replicated from the same
       machine
To: slony <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Well, I'm not getting any bites on this issue, so either I'm the first
person to try this, or I have bad breath.. ;)

Quick question.  Is the slony_tools.conf file only used at
initialization and startup of the slony processes?  That is, once I've
got my replication up and running, is the slony_tools.conf file
referenced again?  The point is, I'm thinking that I can create multiple
slony_tools.conf files, one for each database.  Link the appropriate one
during the startup of slony for that database, then move on to the next
database once that replication is going for the first one.

It appears to me that the slony_tools.conf file is simply a perl module
that must be referenced by the code, so I'm assuming I can make this
work, I just don't want to be hacking a bunch of different scripts.

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
 - Benjamin Franklin






------------------------------------------------------------------------

_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general


--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
 - Benjamin Franklin
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general

Reply via email to