List:General Discussion« Previous MessageNext Message »
From:Rick James Date:May 2 2012 7:00pm
Subject:RE: Can the mysql replication limited to one database
View as plain text  
Nothing in the slave's my.cnf.

On the Master, binlog-do/ignore-* filters before leaving the Master.
On the Slave, replicate-do/ignore-* (if used) would filter after getting to the Slave.

That is, you _could_ do the replicate-* instead of the binlog-*, but that would be
inefficient.  Doing both is redundant.

> -----Original Message-----
> From: Brown, Charles [mailto:CBrown@stripped]
> Sent: Wednesday, May 02, 2012 11:15 AM
> To: Rick James
> Cc: mysql@stripped
> Subject: RE: Can the mysql replication limited to one database
> 
> Hello Rick,
> What goes into your my.cnf slave  ?
> Given dbname1 and dbname2
> 
> 
> 
> 
> -----Original Message-----
> From: Rick James [mailto:rjames@stripped]
> Sent: Wednesday, May 02, 2012 12:05 PM
> To: Brown, Charles
> Cc: mysql@stripped
> Subject: RE: Can the mysql replication limited to one database
> 
> Yes, doable.  In my.cnf on master:
>   Binlog-do-database = dbname1
>   Binlog-do-database = dbname2
> Would replicate those two dbs only.
> There are many other combinations using binlog/replicate-do/ignore-
> db/table/wild.  See the manual on replication, and especially the
> flowchart on how those interact (sometimes in unexpected ways).
> 
> > -----Original Message-----
> > From: Brown, Charles [mailto:CBrown@stripped]
> > Sent: Wednesday, May 02, 2012 8:44 AM
> > To: Rick James
> > Cc: mysql@stripped
> > Subject: Can the mysql replication limited to one database
> >
> > Hi Gurus,
> >
> > Can the mysql replication limited to selected schema or database?
> I've
> > been asked to set up mysql for only 1 out 5 databases exist in
> > production. Please advise if this is doable
> >
> > Thanks
> >
> > ********************************************
> > This message is intended only for the use of the Addressee and may
> > contain information that is PRIVILEGED and CONFIDENTIAL.
> >
> > If you are not the intended recipient, you are hereby notified that
> > any dissemination of this communication is strictly prohibited.
> >
> > If you have received this communication in error, please erase all
> > copies of the message and its attachments and notify us immediately.
> >
> > Thank you.
> > ********************************************
> ********************************************
> This message is intended only for the use of the Addressee and may
> contain information that is PRIVILEGED and CONFIDENTIAL.
> 
> If you are not the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited.
> 
> If you have received this communication in error, please erase all
> copies of the message and its attachments and notify us immediately.
> 
> Thank you.
> ********************************************
Thread
RFE: Allow to use version-specific my.cnf filesHonza Horak25 Apr
  • Re: RFE: Allow to use version-specific my.cnf filesAndrĂ©s Tello25 Apr
    • Re: RFE: Allow to use version-specific my.cnf filesHonza Horak27 Apr
      • Re: RFE: Allow to use version-specific my.cnf filesShawn Green27 Apr
        • engine is now innoDB instead of MyISAM. Charles Brown28 Apr
          • Re: engine is now innoDB instead of MyISAM.Reindl Harald28 Apr
            • RE: engine is now innoDB instead of MyISAM.Charles Brown28 Apr
              • Re: engine is now innoDB instead of MyISAM.Claudio Nanni28 Apr
        • Re: RFE: Allow to use version-specific my.cnf filesHonza Horak2 May
    • RE: RFE: Allow to use version-specific my.cnf filesRick James2 May
      • Can the mysql replication limited to one database Charles Brown2 May
        • Re: Can the mysql replication limited to one databasea.smith2 May
          • RE: Can the mysql replication limited to one databaseRick James2 May
            • using the bin-log approach on the master side, how can I accomplishmy replication objectivesCharles Brown3 May
              • Re: using the bin-log approach on the master side, how can I accomplish my replication objectivesNitin Mehta3 May
        • RE: Can the mysql replication limited to one database Rick James2 May
          • Re: Can the mysql replication limited to one databaseClaudio Nanni2 May
            • Re: Can the mysql replication limited to one databaseSinger X.J. Wang2 May
            • RE: Can the mysql replication limited to one databaseRick James2 May
          • RE: Can the mysql replication limited to one database Charles Brown2 May
            • RE: Can the mysql replication limited to one database Rick James2 May
Re: engine is now innoDB instead of MyISAM.Claudio Nanni29 Apr
  • RE: engine is now innoDB instead of MyISAM.Charles Brown29 Apr
    • Re: engine is now innoDB instead of MyISAM.Reindl Harald29 Apr
      • Re: engine is now innoDB instead of MyISAM.Charles Brown29 Apr
        • Re: engine is now innoDB instead of MyISAM.Michael Dykman30 Apr
    • RE: engine is now innoDB instead of MyISAM.Claudio Nanni29 Apr
      • RE: engine is now innoDB instead of MyISAM.Rick James30 Apr
Re: using the bin-log approach on the master side, how can I accomplish my replication objectivesNitin Mehta3 May
  • RE: using the bin-log approach on the master side, how can Iaccomplish my replication objectivesCharles Brown3 May
    • Re: using the bin-log approach on the master side, how can I accomplish my replication objectivesNitin Mehta3 May
  • master BIN-LOG maintenaceCharles Brown3 May
    • Re: master BIN-LOG maintenaceNitin Mehta3 May
      • RE: master BIN-LOG maintenaceRick James3 May
  • RE: using the bin-log approach on the master side, how can Iaccomplish my replication objectivesRick James3 May