<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: My MySQL Binary Log files are taking up all my disk space!</title>
	<atom:link href="http://systembash.com/content/mysql-binary-log-file-size-huge/feed/" rel="self" type="application/rss+xml" />
	<link>http://systembash.com/content/mysql-binary-log-file-size-huge/</link>
	<description>Technology and System Administration</description>
	<lastBuildDate>Thu, 29 Jul 2010 09:20:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Tony Palmer</title>
		<link>http://systembash.com/content/mysql-binary-log-file-size-huge/comment-page-1/#comment-37146</link>
		<dc:creator>Tony Palmer</dc:creator>
		<pubDate>Fri, 31 Jul 2009 13:16:56 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/content/mysql-binary-log-file-size-huge/#comment-37146</guid>
		<description>If you are regularily dealing with large imports of data e.g. load data infile and have binary logging enabled remember that for a file of size x your db file will be at least size x, binary log at least size x and also your indexes will take up space. Therefore a file of size x you could require up to 3x disk capacity. Note that if you are reloading the data several times in a short period of time for testing purposes deleteing the tables will not purge the log, your disk space will get chewed up pretty fast! Consider issueing the command purge binary logs before &#039;2009-07-31&#039;; command...</description>
		<content:encoded><![CDATA[<p>If you are regularily dealing with large imports of data e.g. load data infile and have binary logging enabled remember that for a file of size x your db file will be at least size x, binary log at least size x and also your indexes will take up space. Therefore a file of size x you could require up to 3x disk capacity. Note that if you are reloading the data several times in a short period of time for testing purposes deleteing the tables will not purge the log, your disk space will get chewed up pretty fast! Consider issueing the command purge binary logs before &#8217;2009-07-31&#8242;; command&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andyj</title>
		<link>http://systembash.com/content/mysql-binary-log-file-size-huge/comment-page-1/#comment-18205</link>
		<dc:creator>andyj</dc:creator>
		<pubDate>Wed, 08 Oct 2008 08:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/content/mysql-binary-log-file-size-huge/#comment-18205</guid>
		<description>Binary logs are also useful for backups, where they are used to provide incremental backup and support snapshot backups.</description>
		<content:encoded><![CDATA[<p>Binary logs are also useful for backups, where they are used to provide incremental backup and support snapshot backups.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dinesh kaushik</title>
		<link>http://systembash.com/content/mysql-binary-log-file-size-huge/comment-page-1/#comment-15148</link>
		<dc:creator>dinesh kaushik</dc:creator>
		<pubDate>Tue, 05 Aug 2008 05:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://systembash.com/content/mysql-binary-log-file-size-huge/#comment-15148</guid>
		<description>After commenting log-bin=mysql-bin in /etc/my.cnf file i am not able to stop of generation of mysql-bin log file that are generated in /var/lib/mysql folder</description>
		<content:encoded><![CDATA[<p>After commenting log-bin=mysql-bin in /etc/my.cnf file i am not able to stop of generation of mysql-bin log file that are generated in /var/lib/mysql folder</p>
]]></content:encoded>
	</item>
</channel>
</rss>
