slony and database replication (info from LinuxWorld)
Python
python at venix.com
Tue Apr 11 18:38:01 EDT 2006
My two main reasons for using MySQL are:
easy administration
replication
The MySQL replication process works by serving the Master's log out to
the replicating slaves over the network. The connection is very loose.
So long as the log files have not been deleted, a slave can resume
processing even after losing contact for several months. The log file
includes time stamp info from the original server along with server ID
numbers so that (master, replicator) sets can be daisy chained or even
closed into a circle.
I asked about replication for postgresql and was pointed to Slony.
However, reading the website info, Slony appears to be designed for
tightly coupled on-line cluster style operations.
If anyone cares, the rules for MySQL replication are:
unique ID for each server
only one master (source) for each server
--
Lloyd Kvam
Venix Corp
More information about the gnhlug-discuss
mailing list