{"id":476,"date":"2005-09-30T14:58:20","date_gmt":"2005-09-30T04:58:20","guid":{"rendered":"http:\/\/www.flamingspork.com\/blog\/?p=476"},"modified":"2013-12-18T08:42:50","modified_gmt":"2013-12-17T22:42:50","slug":"the-bastedo-blog-replication-in-mysql-5","status":"publish","type":"post","link":"https:\/\/www.flamingspork.com\/blog\/2005\/09\/30\/the-bastedo-blog-replication-in-mysql-5\/","title":{"rendered":"the bastedo blog – replication in mysql 5"},"content":{"rendered":"

the bastedo blog<\/a><\/p>\n

(I did matching versions [5.x] don’t know how diff versions will work) <\/p><\/blockquote>\n

Setting up a slave with a newer version of MySQL is quite a common setup. It has a couple of advantages:
\n– it lests you test a new version before deploying on the master (to test that everything goes smoothly)
\n– it lets you test new major versions (e.g. 5.0) before they are released GA (helps find bugs that may affect your setup).<\/p>\n

I know at least one customer generally has a slave runnin the latest BK tree – just to be sure that nothing is going to even potentially break for them. Kudos to them :)<\/p>\n

Having a slave that you use for backups is a great idea. No extra load on the master (i.e. you can safely stop the db on the slave and back things up quickly – without having locks held on your master!).<\/p>\n

Also, if your master suffers a meltdown, you have a recent live backup system ready to take its place!<\/p>\n","protected":false},"excerpt":{"rendered":"

the bastedo blog (I did matching versions [5.x] don’t know how diff versions will work) Setting up a slave with a newer version of MySQL is quite a common setup. It has a couple of advantages: – it lests you … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1,14],"tags":[],"class_list":["post-476","post","type-post","status-publish","format-standard","hentry","category-general","category-mysql"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p5a6n8-7G","jetpack-related-posts":[{"id":2223,"url":"https:\/\/www.flamingspork.com\/blog\/2010\/12\/06\/replication-log-inside-innodb\/","url_meta":{"origin":476,"position":0},"title":"Replication log inside InnoDB","author":"Stewart Smith","date":"2010-12-06","format":false,"excerpt":"The MySQL replication system has always had the replication log (\"binlog\") as a separate set of files on disk. Originally, this really didn't matter as, well, MyISAM wasn't transactional or crash safe so the binlog didn't need to be either. If you crashed on a busy write workload, your replication\u2026","rel":"","context":"In "drizzle"","block_context":{"text":"drizzle","link":"https:\/\/www.flamingspork.com\/blog\/category\/work-et-al\/drizzle-work-et-al\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":658,"url":"https:\/\/www.flamingspork.com\/blog\/2006\/04\/19\/rusty-on-floating-point-and-keeping-neat-code\/","url_meta":{"origin":476,"position":1},"title":"Rusty on floating point (and keeping neat code)","author":"Stewart Smith","date":"2006-04-19","format":false,"excerpt":"Rusty talks about the \"fun\" of floating point and how this all ties into Wesnoth. Platform consistency is certainly a good thing - so I'm guessing the attack_prediction code isn't run by each node in a network game in a way where machines could disagree on the outcome. This does\u2026","rel":"","context":"In "mysql"","block_context":{"text":"mysql","link":"https:\/\/www.flamingspork.com\/blog\/category\/work-et-al\/mysql\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3738,"url":"https:\/\/www.flamingspork.com\/blog\/2014\/05\/26\/awesome-mysql-5-7-improvements\/","url_meta":{"origin":476,"position":2},"title":"Awesome MySQL 5.7 improvements","author":"Stewart Smith","date":"2014-05-26","format":false,"excerpt":"Recently, I've had reason to poke at MySQL performance on some pretty cool hardware. Comparing MySQL 5.6 to MySQL 5.7 is a pretty interesting thing to do when you have many CPU cores. The improvements to creating read views in InnoDB is absolutely huge for small statements with large concurrency\u2026","rel":"","context":"In "code"","block_context":{"text":"code","link":"https:\/\/www.flamingspork.com\/blog\/category\/code\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3238,"url":"https:\/\/www.flamingspork.com\/blog\/2013\/03\/06\/mariadb-code-size\/","url_meta":{"origin":476,"position":3},"title":"MariaDB code size","author":"Stewart Smith","date":"2013-03-06","format":false,"excerpt":"Continuing on from my previous post,\u00c2\u00a0MySQL code size over releases. I wanted to look at the different branches\/patch sets of MySQL out there and work out how far from upstream they deviated. I'm just going to compare against whatever upstream version the most easily accessible version is based on (be\u2026","rel":"","context":"In "General"","block_context":{"text":"General","link":"https:\/\/www.flamingspork.com\/blog\/category\/general\/"},"img":{"alt_text":"","src":"https:\/\/docs.google.com\/spreadsheet\/oimg?key=0Ar7e3-N2Y32IdHFGRWI2ODk4ZUY4TkhrclJSVC1mb3c&oid=4&zx=imt1yst694nh","width":350,"height":200},"classes":[]},{"id":3705,"url":"https:\/\/www.flamingspork.com\/blog\/2014\/03\/17\/ghosts-of-mysql-past-part-11-why-are-you-happy-about-this\/","url_meta":{"origin":476,"position":4},"title":"Ghosts of MySQL Past, part 11: Why are you happy about this?","author":"Stewart Smith","date":"2014-03-17","format":false,"excerpt":"This is part 11 in what's shaping up to be the best part of a 6 week series (Part 1, 2, 3, 4, 5, 6, 7, 7.1, 8, 8.1, 9 and 10) on various history bits of MySQL, somewhat following my LCA2014 talk (video here). One of my favorite MySQL\u2026","rel":"","context":"In "mysql"","block_context":{"text":"mysql","link":"https:\/\/www.flamingspork.com\/blog\/category\/work-et-al\/mysql\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2362,"url":"https:\/\/www.flamingspork.com\/blog\/2011\/04\/21\/http-json-alsosql-interface-to-drizzle\/","url_meta":{"origin":476,"position":5},"title":"HTTP JSON AlsoSQL interface to Drizzle","author":"Stewart Smith","date":"2011-04-21","format":false,"excerpt":"So... I had another one of those \"hrrm... this shouldn't be hard to hack a proof-of-concept\" moments. Web apps are increasingly speaking JSON all around the place. Why can't we speak JSON to\/from the database? Why? Seriously, why not? One reason why MongoDB has found users is that JSON is\u2026","rel":"","context":"In "drizzle"","block_context":{"text":"drizzle","link":"https:\/\/www.flamingspork.com\/blog\/category\/work-et-al\/drizzle-work-et-al\/"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/www.flamingspork.com\/blog\/wp-content\/uploads\/2011\/04\/Screenshot-11-300x230.png?resize=350%2C200","width":350,"height":200},"classes":[]}],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/posts\/476","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/comments?post=476"}],"version-history":[{"count":1,"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/posts\/476\/revisions"}],"predecessor-version":[{"id":3555,"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/posts\/476\/revisions\/3555"}],"wp:attachment":[{"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/media?parent=476"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/categories?post=476"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.flamingspork.com\/blog\/wp-json\/wp\/v2\/tags?post=476"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}