slave.
The slave server is running MySQL 4.0.20.
Eamon Daly
- Original Message -
From: "Keith Ivey" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, March 09, 2005 2:11 PM
Subject: Re: safe way of replication?
At
Atle Veka wrote:
Even if you replicate the 'mysql' DB, GRANT/REVOKE statements are not
replicated, nor are FLUSH statements. So if you are adding new access
privileges on the master they will not be active on the slave until you
issue FLUSH PRIVILEGES (one the slave).
What version are you talking a
Even if you replicate the 'mysql' DB, GRANT/REVOKE statements are not
replicated, nor are FLUSH statements. So if you are adding new access
privileges on the master they will not be active on the slave until you
issue FLUSH PRIVILEGES (one the slave).
Hope this helps. :)
Atle
-
Flying Crocodile
aving those
problem.
I'll stop replicating mysql tables then... Thanks ;)
--
Chris.
- Original Message -
From: "Gary Richardson" <[EMAIL PROTECTED]>
To: "Chris Knipe" <[EMAIL PROTECTED]>
Cc:
Sent: Wednesday, March 09, 2005 6:23 PM
Subject: Re: safe way
I would probably not replica the mysql database in your case.
We run a similar setup. One problem we have is people connecting to
the wrong database server and applying updates (for example, they
think they are in the master, but it's really the slave and they
perform an update or an insert). As y
Lo all,
Just wondering... Would the below be considered a "safe" way to do
replication...
MasterBD: One Database (most Critical)
SlaveDB: Replicating all databases from MasterBD as well as hosting allot of
other 3rd party, or customer DBs.
Basically, the MasterBD holds a single critical databa
