<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The I_S.INNODB_BUFFER_PAGE on FromDual GmbH</title><link>https://www.fromdual.com/blog/shrinking-innodb-system-tablespace-file-ibdata1-poc/comment-662/</link><description>Recent content in The I_S.INNODB_BUFFER_PAGE on FromDual GmbH</description><generator>Hugo</generator><language>en-GB</language><managingEditor>oli.sennhauser@fromdual.com (Oli Sennhauser)</managingEditor><webMaster>oli.sennhauser@fromdual.com (Oli Sennhauser)</webMaster><copyright>© FromDual GmbH</copyright><lastBuildDate>Tue, 11 Dec 2012 08:49:16 +0200</lastBuildDate><atom:link href="https://www.fromdual.com/blog/shrinking-innodb-system-tablespace-file-ibdata1-poc/comment-662/index.xml" rel="self" type="application/rss+xml"/><item><title>The I_S.INNODB_BUFFER_PAGE</title><link>https://www.fromdual.com/blog/shrinking-innodb-system-tablespace-file-ibdata1-poc/comment-662/</link><pubDate>Tue, 11 Dec 2012 08:49:17 +0200</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/shrinking-innodb-system-tablespace-file-ibdata1-poc/comment-662/</guid><description>&lt;p&gt;The I_S.INNODB_BUFFER_PAGE query seems unsafe to me, as it queries the buffer pool and not the tablespace. The innochecksum approach to find unused pages at the end to truncate + header field patching seems to be as OK as it could possibly be given the method.&lt;/p&gt;
&lt;p&gt;It seems that implementing the truncate of unused tablespace trailer would not be that hard (say, in XtraDB), and compacting with page relocation should be possible too with more effort. I wonder if it&amp;rsquo;s on InnoDB roadmap.&lt;/p&gt;</description></item></channel></rss>