On Tue, 2005-08-09 at 21:04, Vincent Chen wrote:
> Hi, all
> 
> I just setup a postgresql cluster and some questions come to me:
> 
> 1. slon running on foreground and keep showing logs, how can I configure slon
> run on background as daemon?

There are some scripts that come with slon to do that.  

> 2. my test environment has 1 master and 1 slave node. if I need to add another
> slave node, how can I do that?

I'm pretty sure this is handled in the basic documentation.  And as
someone else mentioned, there is not master and slave, just subscribers
and providers.

> 3. mysql also has replication ability. what's the difference between these 2
> DBMS cluster solution?

Slony works reliably?  Just do a search on google or the mysql mailing
lists for reports of mysql replication failing mysteriously, with no
error messages or anything.

Also, slony allows you to take a live db, apply replication, get the
subscriber up to speed, and then switch over with  minimal downtime.

MySQL requires you to down the master, make the slave an exact copy, and
then start them both up.  Any problem with replication will require you
to repeat this process.  ugh.

Slony is a well thought out, third or so generation of replication for
PostgreSQL, and it's designers learned from the mistakes made in
previous replication systems.

MySQL's replication had to get out the door because marketing said so,
bumps and warts and all.  They're mostly all still there.