<?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"
	>
<channel>
	<title>Comments on: MySQL Row &#038; Data Limits</title>
	<atom:link href="http://rackerhacker.com/2007/01/04/mysql-row-data-limits/feed/" rel="self" type="application/rss+xml" />
	<link>http://rackerhacker.com/2007/01/04/mysql-row-data-limits/</link>
	<description>Words of wisdom from a server administrator</description>
	<pubDate>Sun, 12 Oct 2008 01:42:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: major</title>
		<link>http://rackerhacker.com/2007/01/04/mysql-row-data-limits/#comment-431</link>
		<dc:creator>major</dc:creator>
		<pubDate>Sun, 02 Mar 2008 15:48:33 +0000</pubDate>
		<guid isPermaLink="false">http://fix.mhtx.net/2007/01/04/mysql-row-data-limits/#comment-431</guid>
		<description>Good points, Scott!  I had forgotten about the pointer size changes in MySQL 5.</description>
		<content:encoded><![CDATA[<p>Good points, Scott!  I had forgotten about the pointer size changes in MySQL 5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scottg</title>
		<link>http://rackerhacker.com/2007/01/04/mysql-row-data-limits/#comment-430</link>
		<dc:creator>scottg</dc:creator>
		<pubDate>Sun, 02 Mar 2008 03:47:10 +0000</pubDate>
		<guid isPermaLink="false">http://fix.mhtx.net/2007/01/04/mysql-row-data-limits/#comment-430</guid>
		<description>I believe all this applies only to MySQL 4 and prior versions.  

In MySQL 5, the default pointer size was increased to 6 bytes (48 bits), allowing for tables up to 256TB (assuming your filesystem allows files this large).  The pointer can even be set to 7 bytes, allowing for a table size of up to 65,536TB. (please be patient, your backup completion time over gigabit ethernet is estimated at 16.6 years)

You can check the default row pointer size  with "SHOW GLOBAL VARIABLES LIKE  'myisam_data_pointer_size'; ".   This will show the default pointer size in bytes.  This parameter, can of course,  be changed in your my.cnf if you would like a different default.

Conversely, if you need to squeeze every bit of performance out of your system, you can set the row pointer size down as low as 2 bytes for tables which you are confident will never grow very large.  This will save 4 bytes per row in the datafile and each index.

The row pointer size of a table can be adjusted using the "ALTER TABLE" technique described in the main post.</description>
		<content:encoded><![CDATA[<p>I believe all this applies only to MySQL 4 and prior versions.  </p>
<p>In MySQL 5, the default pointer size was increased to 6 bytes (48 bits), allowing for tables up to 256TB (assuming your filesystem allows files this large).  The pointer can even be set to 7 bytes, allowing for a table size of up to 65,536TB. (please be patient, your backup completion time over gigabit ethernet is estimated at 16.6 years)</p>
<p>You can check the default row pointer size  with &#8220;SHOW GLOBAL VARIABLES LIKE  &#8216;myisam_data_pointer_size&#8217;; &#8220;.   This will show the default pointer size in bytes.  This parameter, can of course,  be changed in your my.cnf if you would like a different default.</p>
<p>Conversely, if you need to squeeze every bit of performance out of your system, you can set the row pointer size down as low as 2 bytes for tables which you are confident will never grow very large.  This will save 4 bytes per row in the datafile and each index.</p>
<p>The row pointer size of a table can be adjusted using the &#8220;ALTER TABLE&#8221; technique described in the main post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan B</title>
		<link>http://rackerhacker.com/2007/01/04/mysql-row-data-limits/#comment-10</link>
		<dc:creator>Dan B</dc:creator>
		<pubDate>Tue, 14 Aug 2007 17:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://fix.mhtx.net/2007/01/04/mysql-row-data-limits/#comment-10</guid>
		<description>Why not switch the storage engine to InnoDB then you can have the same table with many rows?</description>
		<content:encoded><![CDATA[<p>Why not switch the storage engine to InnoDB then you can have the same table with many rows?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
