<?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; innodb_buffer_pool_size</title>
	<atom:link href="http://www.pythian.com/news/tag/innodb_buffer_pool_size/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>InnoDB error : Total number of locks exceeds the lock table size</title>
		<link>http://www.pythian.com/news/22699/innodb-error-total-number-of-locks-exceeds-the-lock-table-size/</link>
		<comments>http://www.pythian.com/news/22699/innodb-error-total-number-of-locks-exceeds-the-lock-table-size/#comments</comments>
		<pubDate>Thu, 19 May 2011 05:32:07 +0000</pubDate>
		<dc:creator>Suresh Kuna</dc:creator>
				<category><![CDATA[Group Blog Posts]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Pythian]]></category>
		<category><![CDATA[Technical Blog]]></category>
		<category><![CDATA[Innodb table locks]]></category>
		<category><![CDATA[innodb_buffer_pool_size]]></category>
		<category><![CDATA[locks]]></category>
		<category><![CDATA[show engine innodb status]]></category>
		<category><![CDATA[table size]]></category>

		<guid isPermaLink="false">http://www.pythian.com/news/?p=22699</guid>
		<description><![CDATA[Recently, one of our customers had a problem with one of their replication slaves where a sql statement gave an error while executing on the slave which was executed successfully on the Master server. The slave stopped with the error as below. mysql&#62; show slave status\G *************************** 1. row *************************** Slave_IO_State: Waiting for master to [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/22699/innodb-error-total-number-of-locks-exceeds-the-lock-table-size/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MySQL Memory Consumption</title>
		<link>http://www.pythian.com/news/1455/mysql-memory-consumption/</link>
		<comments>http://www.pythian.com/news/1455/mysql-memory-consumption/#comments</comments>
		<pubDate>Fri, 23 Jan 2009 22:37:14 +0000</pubDate>
		<dc:creator>Keith Murphy</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[cacti]]></category>
		<category><![CDATA[Ganglia]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[innodb_buffer_pool_size]]></category>
		<category><![CDATA[key_buffer_size]]></category>
		<category><![CDATA[memory]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1455/mysql-memory-consumption</guid>
		<description><![CDATA[Had an interesting situation come up today with a client. We had a situation where a server crashed because it ran out of memory. The calculation we used to monitor memory usage did not take into account all factors. When looking at this, I noticed a couple of things: There are numerous calculations available online. [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1455/mysql-memory-consumption/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>InnoDB Transactional Characteristics</title>
		<link>http://www.pythian.com/news/1104/innodb-transactional-characteristics/</link>
		<comments>http://www.pythian.com/news/1104/innodb-transactional-characteristics/#comments</comments>
		<pubDate>Tue, 01 Jul 2008 19:00:03 +0000</pubDate>
		<dc:creator>Keith Murphy</dc:creator>
				<category><![CDATA[MySQL]]></category>
		<category><![CDATA[InnoDB]]></category>
		<category><![CDATA[innodb_buffer_pool_size]]></category>
		<category><![CDATA[innodb_data_file_path]]></category>
		<category><![CDATA[innodb_data_home_dir]]></category>
		<category><![CDATA[innodb_file_per_table]]></category>
		<category><![CDATA[innodb_flush_log_at_trx_commit]]></category>
		<category><![CDATA[innodb_log_file_size]]></category>
		<category><![CDATA[MVCC]]></category>
		<category><![CDATA[page-level locking]]></category>
		<category><![CDATA[row-level locking]]></category>
		<category><![CDATA[table-level locking]]></category>

		<guid isPermaLink="false">http://www.pythian.com/blogs/1104/innodb-transactional-characteristics</guid>
		<description><![CDATA[InnoDB is a storage engine that uses MVCC (described shortly) to provide ACID-compliant transactional data storage using row-level locking.  MVCC stands for Multi-Version Concurrency Control.  It is how InnoDB allows multiple transactions to look at a data set of one or more tables and have a consistent view of the data. MVCC keeps a virtual [...]]]></description>
		<wfw:commentRss>http://www.pythian.com/news/1104/innodb-transactional-characteristics/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

