You should keep those procedures in a different database, not mysql. Then you can avoid replication with replication filters: https://mariadb.com/kb/en/mariadb/selectively-skipping-replication-of-binlog... But first, be sure you understand what happens when you call the procedure on the master. Federico -------------------------------------------- Lun 29/8/16, Игорь Пашев <pashev.igor@gmail.com> ha scritto: Oggetto: Re: [Maria-discuss] Don't replicate procedures in the mysql database A: "Daniel Black" <daniel.black@au1.ibm.com> Cc: "MariaDB discuss" <maria-discuss@lists.launchpad.net> Data: Lunedì 29 agosto 2016, 15:44 2016-08-29 1:25 GMT+03:00 Daniel Black <daniel.black@au1.ibm.com>:

A question for you is why is it important not to have it on the slave?

Because the slave already has this procedure with a slightly different implementation, and different owner (definer).

If the slave is a failover it should have the procedure.

...

When I execute `CREATE PROCEDURE mysql.bar` on the master,

If I wanted a failover server I would not be fiddling with replication options and channels at all. this

...

procedure appears on the slave.

Which is what replication is meant to do.

This is not consistent with creating and modifying mysql users. That's why I'm asking.

Its probably also best not to populate the mysql database with your stored procedures.

It's totally fine for maintenance procedures. See for example http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Appendix.MySQL.SQLRef....

set session sql_log_bin=0; create procedure...

This is not scalable and sometime impossible: for the SUPER privilege, at Amazon RDS, it could break other slaves. _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to     : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help   : https://help.launchpad.net/ListHelp