<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Pythian Blog &#187; show slave status</title>
	<atom:link href="http://www.pythian.com/news/tag/show-slave-status/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Fri, 10 Feb 2012 09:54:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>MySQL: Using CONNECT to Quickly Verify Replication Health</title>
		<link>http://www.pythian.com/news/1466/mysql-using-connect-to-quickly-verify-replication-health/</link>
		<comments>http://www.pythian.com/news/1466/mysql-using-connect-to-quickly-verify-replication-health/#comments</comments>
		<pubDate>Tue, 27 Jan 2009 23:44:33 +0000</pubDate>
		<dc:creator>Gerry Narvaja</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[CONNECT]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[show slave status]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1466/mysql-using-connect-to-quickly-verify-replication-health</guid>
		<description><![CDATA[One very helpful use of the technique Sheeri described in Remote connections without leaving the mysql shell is making sure that replication is working properly. According to the MySQL Reference Manual&#8217;s section on SHOW SLAVE STATUS Syntax, it shows information corresponding to the slave thread in the slave server. When replication is broken, however, or [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1466/mysql-using-connect-to-quickly-verify-replication-health/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>When SHOW SLAVE STATUS and the error log Disagree</title>
		<link>http://www.pythian.com/news/876/when-show-slave-status-and-the-error-log-disagree/</link>
		<comments>http://www.pythian.com/news/876/when-show-slave-status-and-the-error-log-disagree/#comments</comments>
		<pubDate>Fri, 25 Apr 2008 19:03:31 +0000</pubDate>
		<dc:creator>gratton</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[binlog]]></category>
		<category><![CDATA[error log]]></category>
		<category><![CDATA[show slave status]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/876/when-show-slave-status-and-the-error-log-disagree</guid>
		<description><![CDATA[Or, When MySQL Lies! When I do a show slave status\G, sometimes mysqld will lie to me and give me a wrong Exec_Master_Log_Pos. Let me explain with a situation from last night. This is the output of show slave status\G from mysql version 5.0.41-community-log: mysql&#62; show slave status \G *************************** 1. row *************************** Slave_IO_State: Waiting [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/876/when-show-slave-status-and-the-error-log-disagree/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

