<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Flushing on FromDual GmbH</title><link>https://www.fromdual.com/tags/flushing/</link><description>Recent content in Flushing 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>Thu, 10 Dec 2020 17:38:36 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/flushing/index.xml" rel="self" type="application/rss+xml"/><item><title>How to force InnoDB Buffer Pool flushing</title><link>https://www.fromdual.com/blog/how-to-force-innodb-buffer-pool-flushing/</link><pubDate>Thu, 10 Dec 2020 17:38:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/how-to-force-innodb-buffer-pool-flushing/</guid><description>&lt;p&gt;InnoDB tries to keep pages in Buffer Pool to be fast. If a page is changed by a DML statement (&lt;code&gt;INSERT, UPDATE, DELETE&lt;/code&gt;) this change will be done in InnoDB Buffer Pool and not directly on disk. But those changed InnoDB pages residing in InnoDB Buffer Pool must be flushed sooner or later to disk to become persistent. This is done by the InnoDB background writer thread(s) (default 4).&lt;/p&gt;</description></item><item><title>InnoDB Page Cleaner intended loop takes too long</title><link>https://www.fromdual.com/blog/innodb-page-cleaner-intended-loop-takes-too-long/</link><pubDate>Tue, 18 Feb 2020 17:50:55 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-page-cleaner-intended-loop-takes-too-long/</guid><description>&lt;p&gt;Recently we migrated a database system from MySQL 5.7 to MariaDB 10.3. Everything went fine so far just the following message started to pop-up in the MariaDB Error Log File with the severity &lt;strong&gt;Note&lt;/strong&gt;:&lt;/p&gt;</description></item></channel></rss>