MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon Date:April 19 2008 4:49pm
Subject:svn commit - mysqldoc@docsrva: r10551 - in trunk: it/refman-5.1 pt/refman-5.1 refman-5.1 refman-6.0
View as plain text  
Author: jstephens
Date: 2008-04-19 18:49:54 +0200 (Sat, 19 Apr 2008)
New Revision: 10551

Log:

Updated info about replication and statements altering privileges (see 
Bug #36118)

(Thanks, JasonH!)



Modified:
   trunk/it/refman-5.1/renamed-nodes.txt
   trunk/it/refman-5.1/replication-notes.xml
   trunk/pt/refman-5.1/renamed-nodes.txt
   trunk/pt/refman-5.1/replication-notes.xml
   trunk/refman-5.1/renamed-nodes.txt
   trunk/refman-5.1/replication-notes.xml
   trunk/refman-6.0/renamed-nodes.txt
   trunk/refman-6.0/replication-notes.xml


Modified: trunk/it/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/it/refman-5.1/renamed-nodes.txt	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/it/refman-5.1/renamed-nodes.txt	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 439 bytes

@@ -21,4 +21,5 @@
 #
 
 replication-features-autoincid replication-features-auto-increment 2009-04-01
+replication-features-mysqldb replication-features-privileges 2009-05-01
 


Modified: trunk/it/refman-5.1/replication-notes.xml
===================================================================
--- trunk/it/refman-5.1/replication-notes.xml	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/it/refman-5.1/replication-notes.xml	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 36, Lines Deleted: 26; 3628 bytes

@@ -1029,39 +1029,49 @@
 
     </section>
 
-    <section id="replication-features-mysqldb">
+    <section id="replication-features-privileges">
 
-      <title>Replication of the System <literal>mysql</literal> Database</title>
+      <title>Replication of Statements Affecting User Privileges</title>
 
       <para>
-        For MySQL 5.1.14 and later, the <literal>mysql</literal>
-        database is not replicated. The <literal>mysql</literal>
-        database is instead seen as a node specific database. Row-based
-        replication is not supported on this table. Instead, statements
-        that would normally update this information (including
-        <literal>GRANT</literal>, <literal>REVOKE</literal> and the
-        manipulation of triggers, stored routines/procedures, and views)
-        are all replicated to slaves using Statement based replication.
+        Replication of statements affecting user privileges &mdash;
+        including <literal>GRANT</literal>, <literal>REVOKE</literal>,
+        <literal>SET PASSWORD</literal>, <literal>CREATE USER</literal>,
+        and <literal>DROP USER</literal> &mdash; behaves as follows:
       </para>
 
-      <para>
-        For MySQL 5.1.13 and earlier, user privileges are replicated
-        only if the <literal>mysql</literal> database is replicated.
-        That is, the <literal>GRANT</literal>,
-        <literal>REVOKE</literal>, <literal>SET PASSWORD</literal>,
-        <literal>CREATE USER</literal>, and <literal>DROP USER</literal>
-        statements take effect on the slave only if the replication
-        setup includes the <literal>mysql</literal> database.
-      </para>
+      <itemizedlist>
 
+        <listitem>
+          <para>
+            These statements are replicated only if the
+            <literal>mysql</literal> database is replicated. If you do
+            not want these statements to be replicated, you should set
+            up the slave not to replicate the <literal>mysql</literal>
+            database; you can do this by starting the slave
+            <command>mysqld</command> with the
+            <option>--replicate-wild-ignore-table=mysql.%</option>
+            option.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            These statements are always replicated using statement-based
+            rplication. This is true even if you are using
+            <option>--binlog-format=ROW</option> on the master.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
       <para>
-        If you're replicating all databases, but don't want statements
-        that affect user privileges to be replicated, set up the slave
-        to not replicate the <literal>mysql</literal> database, using
-        the <option>--replicate-wild-ignore-table=mysql.%</option>
-        option. The slave will recognize that issuing privilege-related
-        SQL statements won't have an effect, and thus not execute those
-        statements.
+        Data-modification statements on tables in the
+        <literal>mysql</literal> database should also be replicated
+        using statement-based replication. However, row-based
+        replication is currently employed for such statements if you use
+        <option>--binlog-format=ROW</option>. This is a known issue; see
+        Bug #36118 for more information.
       </para>
 
     </section>


Modified: trunk/pt/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/pt/refman-5.1/renamed-nodes.txt	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/pt/refman-5.1/renamed-nodes.txt	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 438 bytes

@@ -21,3 +21,4 @@
 #
 
 replication-features-autoincid replication-features-auto-increment 2009-04-01
+replication-features-mysqldb replication-features-privileges 2009-05-01


Modified: trunk/pt/refman-5.1/replication-notes.xml
===================================================================
--- trunk/pt/refman-5.1/replication-notes.xml	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/pt/refman-5.1/replication-notes.xml	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 36, Lines Deleted: 26; 3628 bytes

@@ -1029,39 +1029,49 @@
 
     </section>
 
-    <section id="replication-features-mysqldb">
+    <section id="replication-features-privileges">
 
-      <title>Replication of the System <literal>mysql</literal> Database</title>
+      <title>Replication of Statements Affecting User Privileges</title>
 
       <para>
-        For MySQL 5.1.14 and later, the <literal>mysql</literal>
-        database is not replicated. The <literal>mysql</literal>
-        database is instead seen as a node specific database. Row-based
-        replication is not supported on this table. Instead, statements
-        that would normally update this information (including
-        <literal>GRANT</literal>, <literal>REVOKE</literal> and the
-        manipulation of triggers, stored routines/procedures, and views)
-        are all replicated to slaves using Statement based replication.
+        Replication of statements affecting user privileges &mdash;
+        including <literal>GRANT</literal>, <literal>REVOKE</literal>,
+        <literal>SET PASSWORD</literal>, <literal>CREATE USER</literal>,
+        and <literal>DROP USER</literal> &mdash; behaves as follows:
       </para>
 
-      <para>
-        For MySQL 5.1.13 and earlier, user privileges are replicated
-        only if the <literal>mysql</literal> database is replicated.
-        That is, the <literal>GRANT</literal>,
-        <literal>REVOKE</literal>, <literal>SET PASSWORD</literal>,
-        <literal>CREATE USER</literal>, and <literal>DROP USER</literal>
-        statements take effect on the slave only if the replication
-        setup includes the <literal>mysql</literal> database.
-      </para>
+      <itemizedlist>
 
+        <listitem>
+          <para>
+            These statements are replicated only if the
+            <literal>mysql</literal> database is replicated. If you do
+            not want these statements to be replicated, you should set
+            up the slave not to replicate the <literal>mysql</literal>
+            database; you can do this by starting the slave
+            <command>mysqld</command> with the
+            <option>--replicate-wild-ignore-table=mysql.%</option>
+            option.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            These statements are always replicated using statement-based
+            rplication. This is true even if you are using
+            <option>--binlog-format=ROW</option> on the master.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
       <para>
-        If you're replicating all databases, but don't want statements
-        that affect user privileges to be replicated, set up the slave
-        to not replicate the <literal>mysql</literal> database, using
-        the <option>--replicate-wild-ignore-table=mysql.%</option>
-        option. The slave will recognize that issuing privilege-related
-        SQL statements won't have an effect, and thus not execute those
-        statements.
+        Data-modification statements on tables in the
+        <literal>mysql</literal> database should also be replicated
+        using statement-based replication. However, row-based
+        replication is currently employed for such statements if you use
+        <option>--binlog-format=ROW</option>. This is a known issue; see
+        Bug #36118 for more information.
       </para>
 
     </section>


Modified: trunk/refman-5.1/renamed-nodes.txt
===================================================================
--- trunk/refman-5.1/renamed-nodes.txt	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/refman-5.1/renamed-nodes.txt	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 701 bytes

@@ -358,6 +358,7 @@
 replication-features-autoincid replication-features-auto-increment 2009-04-01
 replication-features-diffcolumns replication-features 2009-01-01
 replication-features-morecolumns replication-features 2009-01-01
+replication-features-mysqldb replication-features-privileges 2009-05-01
 replication-formats-mixed binary-log-mixed
 replication-formats-setting binary-log-setting
 replication-mysql-database binary-log-mysql-database


Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/refman-5.1/replication-notes.xml	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 36, Lines Deleted: 26; 3619 bytes

@@ -1070,39 +1070,49 @@
 
     </section>
 
-    <section id="replication-features-mysqldb">
+    <section id="replication-features-privileges">
 
-      <title>Replication of the System <literal>mysql</literal> Database</title>
+      <title>Replication of Statements Affecting User Privileges</title>
 
       <para>
-        For MySQL 5.1.14 and later, the <literal>mysql</literal>
-        database is not replicated. The <literal>mysql</literal>
-        database is instead seen as a node specific database. Row-based
-        replication is not supported on this table. Instead, statements
-        that would normally update this information (including
-        <literal>GRANT</literal>, <literal>REVOKE</literal> and the
-        manipulation of triggers, stored routines/procedures, and views)
-        are all replicated to slaves using Statement based replication.
+        Replication of statements affecting user privileges &mdash;
+        including <literal>GRANT</literal>, <literal>REVOKE</literal>,
+        <literal>SET PASSWORD</literal>, <literal>CREATE USER</literal>,
+        and <literal>DROP USER</literal> &mdash; behaves as follows:
       </para>
 
-      <para>
-        For MySQL 5.1.13 and earlier, user privileges are replicated
-        only if the <literal>mysql</literal> database is replicated.
-        That is, the <literal>GRANT</literal>,
-        <literal>REVOKE</literal>, <literal>SET PASSWORD</literal>,
-        <literal>CREATE USER</literal>, and <literal>DROP USER</literal>
-        statements take effect on the slave only if the replication
-        setup includes the <literal>mysql</literal> database.
-      </para>
+      <itemizedlist>
 
+        <listitem>
+          <para>
+            These statements are replicated only if the
+            <literal>mysql</literal> database is replicated. If you do
+            not want these statements to be replicated, you should set
+            up the slave not to replicate the <literal>mysql</literal>
+            database; you can do this by starting the slave
+            <command>mysqld</command> with the
+            <option>--replicate-wild-ignore-table=mysql.%</option>
+            option.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            These statements are always replicated using statement-based
+            rplication. This is true even if you are using
+            <option>--binlog-format=ROW</option> on the master.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
       <para>
-        If you're replicating all databases, but don't want statements
-        that affect user privileges to be replicated, set up the slave
-        to not replicate the <literal>mysql</literal> database, using
-        the <option>--replicate-wild-ignore-table=mysql.%</option>
-        option. The slave will recognize that issuing privilege-related
-        SQL statements won't have an effect, and thus not execute those
-        statements.
+        Data-modification statements on tables in the
+        <literal>mysql</literal> database should also be replicated
+        using statement-based replication. However, row-based
+        replication is currently employed for such statements if you use
+        <option>--binlog-format=ROW</option>. This is a known issue; see
+        Bug #36118 for more information.
       </para>
 
     </section>


Modified: trunk/refman-6.0/renamed-nodes.txt
===================================================================
--- trunk/refman-6.0/renamed-nodes.txt	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/refman-6.0/renamed-nodes.txt	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 677 bytes

@@ -50,6 +50,7 @@
 replication-features-autoincid replication-features-auto-increment 2009-04-01
 replication-features-diffcolumns replication-features 2009-01-01
 replication-features-morecolumns replication-features 2009-01-01
+replication-features-mysqldb replication-features-privileges 2009-05-01
 restore-table mysql-nutshell
 server-side-overview programs 2009-01-01
 server-startup-programs programs-server 2009-01-01


Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml	2008-04-19 15:35:35 UTC (rev 10550)
+++ trunk/refman-6.0/replication-notes.xml	2008-04-19 16:49:54 UTC (rev 10551)
Changed blocks: 1, Lines Added: 37, Lines Deleted: 17; 3108 bytes

@@ -1038,29 +1038,49 @@
 
     </section>
 
-    <section id="replication-features-mysqldb">
+    <section id="replication-features-privileges">
 
-      <title>Replication of the System <literal>mysql</literal> Database</title>
+      <title>Replication of Statements Affecting User Privileges</title>
 
       <para>
-        The <literal>mysql</literal> database is not replicated. The
-        <literal>mysql</literal> database is instead seen as a node
-        specific database. Row-based replication is not supported on
-        this table. Instead, statements that would normally update this
-        information (including <literal>GRANT</literal>,
-        <literal>REVOKE</literal> and the manipulation of triggers,
-        stored routines/procedures, and views) are all replicated to
-        slaves using Statement based replication.
+        Replication of statements affecting user privileges &mdash;
+        including <literal>GRANT</literal>, <literal>REVOKE</literal>,
+        <literal>SET PASSWORD</literal>, <literal>CREATE USER</literal>,
+        and <literal>DROP USER</literal> &mdash; behaves as follows:
       </para>
 
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            These statements are replicated only if the
+            <literal>mysql</literal> database is replicated. If you do
+            not want these statements to be replicated, you should set
+            up the slave not to replicate the <literal>mysql</literal>
+            database; you can do this by starting the slave
+            <command>mysqld</command> with the
+            <option>--replicate-wild-ignore-table=mysql.%</option>
+            option.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            These statements are always replicated using statement-based
+            rplication. This is true even if you are using
+            <option>--binlog-format=ROW</option> on the master.
+          </para>
+        </listitem>
+
+      </itemizedlist>
+
       <para>
-        If you're replicating all databases, but don't want statements
-        that affect user privileges to be replicated, set up the slave
-        to not replicate the <literal>mysql</literal> database, using
-        the <option>--replicate-wild-ignore-table=mysql.%</option>
-        option. The slave will recognize that issuing privilege-related
-        SQL statements won't have an effect, and thus not execute those
-        statements.
+        Data-modification statements on tables in the
+        <literal>mysql</literal> database should also be replicated
+        using statement-based replication. However, row-based
+        replication is currently employed for such statements if you use
+        <option>--binlog-format=ROW</option>. This is a known issue; see
+        Bug #36118 for more information.
       </para>
 
     </section>


Thread
svn commit - mysqldoc@docsrva: r10551 - in trunk: it/refman-5.1 pt/refman-5.1 refman-5.1 refman-6.0jon19 Apr
  • Re: svn commit - mysqldoc@docsrva: r10551 - in trunk:it/refman-5.1 pt/refman-5.1 refman-5.1 refman-6.0He Zhenxing20 Apr