Author: paul
Date: 2008-04-22 18:29:40 +0200 (Tue, 22 Apr 2008)
New Revision: 10565
Log:
r30904@arctic: paul | 2008-04-22 11:29:43 -0500
Add note regarding caching of memory for system table operations
and that FLUSH PRIVILEGES frees it. (Related to Bug#34789)
Modified:
trunk/it/refman-5.1/optimization.xml
trunk/it/refman-5.1/sql-syntax.xml
trunk/pt/refman-5.1/optimization.xml
trunk/pt/refman-5.1/sql-syntax.xml
trunk/refman-4.1/optimization.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30890
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30865
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30890
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30904
Modified: trunk/it/refman-5.1/optimization.xml
===================================================================
--- trunk/it/refman-5.1/optimization.xml 2008-04-22 14:20:52 UTC (rev 10564)
+++ trunk/it/refman-5.1/optimization.xml 2008-04-22 16:29:40 UTC (rev 10565)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 2; 1694 bytes
@@ -9475,8 +9475,8 @@
Often, it is not possible to predict exactly what indexes will
be required or will be most efficient — actual table
usage is the best indicator. The MySQL Enterprise Monitor
- provides expert advice on this topic. For more information, see
- <ulink url="&base-url-enterprise;advisors.html"/>.
+ provides expert advice on this topic. For more information,
+ see <ulink url="&base-url-enterprise;advisors.html"/>.
</para>
</formalpara>
@@ -16196,6 +16196,22 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ The server caches information in memory as a result of
+ <literal>GRANT</literal>, <literal>CREATE USER</literal>,
+ <literal>CREATE SERVER</literal>, and <literal>INSTALL
+ PLUGIN</literal> statements. This memory is not released by
+ the corresponding <literal>REVOKE</literal>, <literal>DROP
+ USER</literal>, <literal>DROP SERVER</literal>, and
+ <literal>UNINSTALL PLUGIN</literal> statements, so for a
+ server that executes many instances of the statements that
+ cause caching, there will be an increase in memory use. This
+ cached memory can be freed with <literal>FLUSH
+ PRIVILEGES</literal>.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
Modified: trunk/it/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/it/refman-5.1/sql-syntax.xml 2008-04-22 14:20:52 UTC (rev 10564)
+++ trunk/it/refman-5.1/sql-syntax.xml 2008-04-22 16:29:40 UTC (rev 10565)
Changed blocks: 2, Lines Added: 21, Lines Deleted: 7; 2396 bytes
@@ -3951,13 +3951,13 @@
<para>
The older <literal>TYPE</literal> option was synonymous with
<literal>ENGINE</literal>. <literal>TYPE</literal> has been
- deprecated since MySQL 4.0 but is still supported for
- backward compatibility in MySQL 5.1 (excepting MySQL 5.1.7).
- Since MySQL 5.1.8, it produces a warning. It is removed as of
- MySQL 5.2. <emphasis>You should not use
- <literal>TYPE</literal> in any new applications, and you
- should immediately begin conversion of existing applications
- to use <literal>ENGINE</literal> instead</emphasis>. (See
+ deprecated since MySQL 4.0 but is still supported for backward
+ compatibility in MySQL 5.1 (excepting MySQL 5.1.7). Since
+ MySQL 5.1.8, it produces a warning. It is removed as of MySQL
+ 5.2. <emphasis>You should not use <literal>TYPE</literal> in
+ any new applications, and you should immediately begin
+ conversion of existing applications to use
+ <literal>ENGINE</literal> instead</emphasis>. (See
<xref linkend="news-5-1-8"/>.)
</para>
</note>
@@ -24490,6 +24490,20 @@
occurs if the server receives a <literal>SIGHUP</literal>
signal.
</para>
+
+ <para>
+ The server caches information in memory as a result of
+ <literal>GRANT</literal>, <literal>CREATE USER</literal>,
+ <literal>CREATE SERVER</literal>, and <literal>INSTALL
+ PLUGIN</literal> statements. This memory is not released
+ by the corresponding <literal>REVOKE</literal>,
+ <literal>DROP USER</literal>, <literal>DROP
+ SERVER</literal>, and <literal>UNINSTALL PLUGIN</literal>
+ statements, so for a server that executes many instances
+ of the statements that cause caching, there will be an
+ increase in memory use. This cached memory can be freed
+ with <literal>FLUSH PRIVILEGES</literal>.
+ </para>
</listitem>
<listitem>
Modified: trunk/pt/refman-5.1/optimization.xml
===================================================================
--- trunk/pt/refman-5.1/optimization.xml 2008-04-22 14:20:52 UTC (rev 10564)
+++ trunk/pt/refman-5.1/optimization.xml 2008-04-22 16:29:40 UTC (rev 10565)
Changed blocks: 2, Lines Added: 18, Lines Deleted: 2; 1694 bytes
@@ -9475,8 +9475,8 @@
Often, it is not possible to predict exactly what indexes will
be required or will be most efficient — actual table
usage is the best indicator. The MySQL Enterprise Monitor
- provides expert advice on this topic. For more information, see
- <ulink url="&base-url-enterprise;advisors.html"/>.
+ provides expert advice on this topic. For more information,
+ see <ulink url="&base-url-enterprise;advisors.html"/>.
</para>
</formalpara>
@@ -16196,6 +16196,22 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ The server caches information in memory as a result of
+ <literal>GRANT</literal>, <literal>CREATE USER</literal>,
+ <literal>CREATE SERVER</literal>, and <literal>INSTALL
+ PLUGIN</literal> statements. This memory is not released by
+ the corresponding <literal>REVOKE</literal>, <literal>DROP
+ USER</literal>, <literal>DROP SERVER</literal>, and
+ <literal>UNINSTALL PLUGIN</literal> statements, so for a
+ server that executes many instances of the statements that
+ cause caching, there will be an increase in memory use. This
+ cached memory can be freed with <literal>FLUSH
+ PRIVILEGES</literal>.
+ </para>
+ </listitem>
+
</itemizedlist>
<para>
Modified: trunk/pt/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/pt/refman-5.1/sql-syntax.xml 2008-04-22 14:20:52 UTC (rev 10564)
+++ trunk/pt/refman-5.1/sql-syntax.xml 2008-04-22 16:29:40 UTC (rev 10565)
Changed blocks: 2, Lines Added: 21, Lines Deleted: 7; 2396 bytes
@@ -3951,13 +3951,13 @@
<para>
The older <literal>TYPE</literal> option was synonymous with
<literal>ENGINE</literal>. <literal>TYPE</literal> has been
- deprecated since MySQL 4.0 but is still supported for
- backward compatibility in MySQL 5.1 (excepting MySQL 5.1.7).
- Since MySQL 5.1.8, it produces a warning. It is removed as of
- MySQL 5.2. <emphasis>You should not use
- <literal>TYPE</literal> in any new applications, and you
- should immediately begin conversion of existing applications
- to use <literal>ENGINE</literal> instead</emphasis>. (See
+ deprecated since MySQL 4.0 but is still supported for backward
+ compatibility in MySQL 5.1 (excepting MySQL 5.1.7). Since
+ MySQL 5.1.8, it produces a warning. It is removed as of MySQL
+ 5.2. <emphasis>You should not use <literal>TYPE</literal> in
+ any new applications, and you should immediately begin
+ conversion of existing applications to use
+ <literal>ENGINE</literal> instead</emphasis>. (See
<xref linkend="news-5-1-8"/>.)
</para>
</note>
@@ -24490,6 +24490,20 @@
occurs if the server receives a <literal>SIGHUP</literal>
signal.
</para>
+
+ <para>
+ The server caches information in memory as a result of
+ <literal>GRANT</literal>, <literal>CREATE USER</literal>,
+ <literal>CREATE SERVER</literal>, and <literal>INSTALL
+ PLUGIN</literal> statements. This memory is not released
+ by the corresponding <literal>REVOKE</literal>,
+ <literal>DROP USER</literal>, <literal>DROP
+ SERVER</literal>, and <literal>UNINSTALL PLUGIN</literal>
+ statements, so for a server that executes many instances
+ of the statements that cause caching, there will be an
+ increase in memory use. This cached memory can be freed
+ with <literal>FLUSH PRIVILEGES</literal>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-4.1/optimization.xml
===================================================================
Changed blocks: 0, Lines Added: 0, Lines Deleted: 0; 110 bytes
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10565 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 22 Apr |
