<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fpmmm Triggers and Rules on FromDual GmbH</title><link>https://www.fromdual.com/tags/fpmmm-triggers-and-rules/</link><description>Recent content in Fpmmm Triggers and Rules 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>Fri, 26 Nov 2021 16:25:06 +0000</lastBuildDate><atom:link href="https://www.fromdual.com/tags/fpmmm-triggers-and-rules/index.xml" rel="self" type="application/rss+xml"/><item><title>fpmmm Version is old</title><link>https://www.fromdual.com/blog/fpmmm-version-is-old/</link><pubDate>Tue, 24 Dec 2019 08:42:46 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/fpmmm-version-is-old/</guid><description>&lt;p&gt;You are using an old version of the FromDual Performance Monitor for MariaDB and MySQL (fpmmm). Please consider using a &lt;a href="https://www.fromdual.com/taxonomy/term/289" target="_blank" title="Release Tag"&gt;more recent version&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>InnoDB Log Buffer is too small for large transactions</title><link>https://www.fromdual.com/blog/innodb-log-buffer-much-too-small/</link><pubDate>Mon, 23 Dec 2019 14:05:49 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-log-buffer-much-too-small/</guid><description>&lt;p&gt;Your InnoDB Redo Log Buffer is too small for large transactions. Make the InnoDB Redo Log Buffer (&lt;code&gt;innodb_log_buffer_size&lt;/code&gt;) bigger if you have enough RAM available to avoid additional I/O.&lt;br&gt;
1 Mibyte is good for databases with small transactions. 8 Mibyte is good for medium size transactions. 64 MiByte is good for large transactions.&lt;/p&gt;</description></item><item><title>InnoDB plugin is enabled</title><link>https://www.fromdual.com/blog/innodb-plug-in-is-enabled/</link><pubDate>Thu, 16 Jul 2015 20:16:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-plug-in-is-enabled/</guid><description>&lt;p&gt;InnoDB plugin is enabled.&lt;/p&gt;</description></item><item><title>InnoDB Log File size is too small</title><link>https://www.fromdual.com/blog/innodb-log-file-size-is-too-small/</link><pubDate>Thu, 16 Jul 2015 20:15:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-log-file-size-is-too-small/</guid><description>&lt;p&gt;The InnoDB Log File (&lt;code&gt;innodb_log_file_size&lt;/code&gt;) size is possibly too small.&lt;br&gt;
Choosing a too small InnoDB Log File size can have significant write performance impacts.&lt;/p&gt;</description></item><item><title>InnoDB Foreign Key error detected</title><link>https://www.fromdual.com/blog/innodb-foreign-key-error-detected/</link><pubDate>Thu, 16 Jul 2015 20:14:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-foreign-key-error-detected/</guid><description>&lt;p&gt;MySQL (InnoDB, PBXT, NDB, TokuDB) support Foreign Keys to show relatations between tables. Those relations can be enforced through Foreign Key Constraints.&lt;/p&gt;</description></item><item><title>InnoDB Force Recovery is enabled</title><link>https://www.fromdual.com/blog/innodb-force-recovery-is-enabled/</link><pubDate>Thu, 16 Jul 2015 20:12:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-force-recovery-is-enabled/</guid><description>&lt;p&gt;InnoDB Force Recovery (&lt;code&gt;innodb_force_recovery&lt;/code&gt;) is enabled. This mode should be used for data recovery purposes only. It prohibits writing to the data.&lt;/p&gt;</description></item><item><title>InnoDB Flush Log at Transaction Commit</title><link>https://www.fromdual.com/blog/innodb-flush-log-at-transaction-commit/</link><pubDate>Thu, 16 Jul 2015 20:11:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-flush-log-at-transaction-commit/</guid><description>&lt;p&gt;InnoDB Flush Log at Transaction Commit is set to a values != 1. This can lead to a loss of committed transactions in case of a power failure or an unclean shutdown of your database.&lt;/p&gt;</description></item><item><title>InnoDB Deadlock detected</title><link>https://www.fromdual.com/blog/innodb-deadlock-detected/</link><pubDate>Thu, 16 Jul 2015 20:10:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-deadlock-detected/</guid><description>&lt;p&gt;You got an InnoDB Deadlock. Please talk to your development department to fix this problem. Deadlocks are an application problem!&lt;/p&gt;</description></item><item><title>InnoDB Buffer Pool Instances is too small</title><link>https://www.fromdual.com/blog/innodb-buffer-pool-instances-is-too-small/</link><pubDate>Thu, 16 Jul 2015 20:09:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-buffer-pool-instances-is-too-small/</guid><description>&lt;p&gt;If you are using MariaDB/MySQL 5.5 and newer you should use several InnoDB Buffer Pool Instances for performance reasons.&lt;br&gt;
Some rules to size InnoDB Buffer Pool instances are:&lt;/p&gt;</description></item><item><title>Binlog format MIXED with filtering</title><link>https://www.fromdual.com/blog/binlog-format-mixed-with-filtering/</link><pubDate>Wed, 15 Jul 2015 06:11:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/binlog-format-mixed-with-filtering/</guid><description>&lt;p&gt;Binlog format &lt;code&gt;MIXED&lt;/code&gt; changes the binary log format (&lt;code&gt;ROW&lt;/code&gt; or &lt;code&gt;STATEMENT&lt;/code&gt;) depending on the queries (deterministic or not). This makes it impossible to define 100% correctly working binary log filter rules.&lt;/p&gt;</description></item><item><title>Flush time is set</title><link>https://www.fromdual.com/blog/flush-time-is-set/</link><pubDate>Wed, 15 Jul 2015 06:10:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/flush-time-is-set/</guid><description>&lt;p&gt;If the variable &lt;code&gt;flush_time&lt;/code&gt; is set to a non-zero value, all tables are closed (and flushed) every &lt;code&gt;flush_time&lt;/code&gt; seconds to disk. This can cause unnecessary and high I/O spikes.&lt;/p&gt;</description></item><item><title>Table definition cache too small</title><link>https://www.fromdual.com/blog/table-definition-cache-too-small/</link><pubDate>Wed, 15 Jul 2015 06:08:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/table-definition-cache-too-small/</guid><description>&lt;p&gt;The number of table definitions (&lt;code&gt;SHOW CREATE TABLE&amp;lt;br&amp;gt;G&lt;/code&gt;) that can be stored in the table definition cache (&lt;code&gt;table_definition_cache&lt;/code&gt;). If you have a large number of tables (&lt;br&gt;&amp;gt; 400) in your database instance, you should consider a larger table definition cache to increase your database throughput and decrease your query latency.&lt;br&gt;
The command &lt;code&gt;SELECT COUNT(*) FROM information_schema.tables;&lt;/code&gt; shows you how many tables and thus table definitions you have. The global status &lt;code&gt;Open_table_definitions&lt;/code&gt; is the current amount of open table definitions.&lt;/p&gt;</description></item><item><title>Table open cache too small</title><link>https://www.fromdual.com/blog/table-open-cache-too-small/</link><pubDate>Wed, 15 Jul 2015 06:04:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/table-open-cache-too-small/</guid><description>&lt;p&gt;The Table Open Cache (&lt;code&gt;table_open_cache&lt;/code&gt; or old name &lt;code&gt;table_cache&lt;/code&gt;) is a cache to store file handles for all threads. The actual value of cache entries can be seen with the global status of open tables (&lt;code&gt;Open_tables&lt;/code&gt;).&lt;br&gt;
Increasing &lt;code&gt;table_open_cache&lt;/code&gt; increases the number of file descriptors (&lt;code&gt;open_files_limit&lt;/code&gt;) that MySQL requires.&lt;br&gt;
You can check whether you need to increase the Table Open Cache by checking &lt;code&gt;Open_tables&lt;/code&gt; and &lt;code&gt;Opened_tables&lt;/code&gt;. If the value of &lt;code&gt;Opened_tables&lt;/code&gt; is large and you do not use &lt;code&gt;FLUSH TABLES&lt;/code&gt; often (which just forces all tables to be closed and reopened), then you should increase the value of the &lt;code&gt;table_open_cache&lt;/code&gt; variable.&lt;/p&gt;</description></item><item><title>InnoDB Flush Method has changed</title><link>https://www.fromdual.com/blog/innodb-flush-method-has-changed/</link><pubDate>Wed, 01 Jul 2015 10:34:36 +0000</pubDate><author>oli.sennhauser@fromdual.com (Oli Sennhauser)</author><guid>https://www.fromdual.com/blog/innodb-flush-method-has-changed/</guid><description>&lt;p&gt;The InnoDB Flush Method has changed. This can have an impact on InnoDB write Performance.&lt;/p&gt;</description></item></channel></rss>