<?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/"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	
	>
<channel>
	<title>
	Comments on: WordPress DB went too large	</title>
	<atom:link href="https://en.brilliantcode.net/1347/wordpress-db-went-too-large/feed/" rel="self" type="application/rss+xml" />
	<link>https://en.brilliantcode.net/1347/wordpress-db-went-too-large/</link>
	<description></description>
	<lastBuildDate>Wed, 08 Apr 2020 20:01:57 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.2.3</generator>
			<item>
				<title>
				By: Wordpress 資料庫大小猛增 - BrilliantCode.net				</title>
				<link>https://en.brilliantcode.net/1347/wordpress-db-went-too-large/#comment-62</link>
		<dc:creator><![CDATA[Wordpress 資料庫大小猛增 - BrilliantCode.net]]></dc:creator>
		<pubDate>Wed, 08 Apr 2020 19:58:16 +0000</pubDate>
		<guid isPermaLink="false">https://en.brilliantcode.net/?p=1347#comment-62</guid>
					<description><![CDATA[[&#8230;] There is the same post wrote in English, WordPress DB went too large. [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] There is the same post wrote in English, WordPress DB went too large. [&#8230;]</p>
]]></content:encoded>
						</item>
						<item>
				<title>
				By: MySQL #01 binary logs settings &#38; variables - BrilliantCode.net				</title>
				<link>https://en.brilliantcode.net/1347/wordpress-db-went-too-large/#comment-54</link>
		<dc:creator><![CDATA[MySQL #01 binary logs settings &#38; variables - BrilliantCode.net]]></dc:creator>
		<pubDate>Fri, 03 Apr 2020 15:14:24 +0000</pubDate>
		<guid isPermaLink="false">https://en.brilliantcode.net/?p=1347#comment-54</guid>
					<description><![CDATA[[&#8230;] MySQL will cause many critical problems, and that includes database scale grows up abnormally fast(like this post.) So I would introduce some configurations and show how to create events to handle binary log [&#8230;]]]></description>
		<content:encoded><![CDATA[<p>[&#8230;] MySQL will cause many critical problems, and that includes database scale grows up abnormally fast(like this post.) So I would introduce some configurations and show how to create events to handle binary log [&#8230;]</p>
]]></content:encoded>
						</item>
			</channel>
</rss>
