That should work fine, although I'm not sure why you'd want to! They're
going to be in separate databases probably, and separate tables for
sure, so it's not like you're load balancing by using two totally
different database systems.
My only thought there was to have postgres master and mysql slave
running on Server A and mysql master and postgres slave running on
Server B. In a failed situation both would be running on the same
machine. So I was thinking that in normal operation we would be
splitting the reads from the dspam and the dbmail from each other.
It is only a thought at the moment to do that, depending of course
whether postgres is a better / similar choice for dbmail over MySQL or
not. The added complexity just might not be worth it. Looking at the
current load of the current servers (20000 emails per day for 4 700MHz
512Mb RAM mail servers with
amavis/clamav/spamassassin/postfix/vpopmail/nfs and having problems
keeping up) versus the test machines I have (2 x 700MHz 128Mb RAM
servers with dspam/clamav/postfix/dbmail/mysql delivering 20000 emails
with heavy pop access in less than an hour) maybe the destination
servers (2 x 3GHz 2.5Gb RAM) will have no problems at all and I'm
already onto a good thing ;)
Either way it's probably a good idea for me to investigate using
database replication rather than drbd.
Josh.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
