Author: paul
Date: 2006-09-08 21:11:02 +0200 (Fri, 08 Sep 2006)
New Revision: 3308
Log:
IM: Document CREATE INSTANCE, DROP INSTANCE commands. (WL#3158)
Modified:
trunk/refman-5.0/database-administration.xml
trunk/refman-5.1/database-administration.xml
Modified: trunk/refman-5.0/database-administration.xml
===================================================================
--- trunk/refman-5.0/database-administration.xml 2006-09-08 18:47:56 UTC (rev 3307)
+++ trunk/refman-5.0/database-administration.xml 2006-09-08 19:11:02 UTC (rev 3308)
Changed blocks: 4, Lines Added: 17, Lines Deleted: 18; 3193 bytes
@@ -15050,8 +15050,8 @@
<literal>mysql -u <replaceable>other_user</replaceable>
<replaceable>db_name</replaceable></literal> if
<replaceable>other_user</replaceable> has no password. If
- all accounts have a password, connecting using another user's
- account becomes much more difficult.
+ all accounts have a password, connecting using another
+ user's account becomes much more difficult.
</para>
<para>
@@ -19732,11 +19732,11 @@
<listitem>
<para>
- MySQL usernames can be up to 16 characters
- long. This limit is hard-coded in the MySQL servers and
- clients, and trying to circumvent it by modifying the
- definitions of the tables in the <literal>mysql</literal>
- database <emphasis>does not work</emphasis>.
+ MySQL usernames can be up to 16 characters long. This limit
+ is hard-coded in the MySQL servers and clients, and trying
+ to circumvent it by modifying the definitions of the tables
+ in the <literal>mysql</literal> database <emphasis>does not
+ work</emphasis>.
</para>
<para>
@@ -27066,10 +27066,9 @@
</para>
<para>
- Cache entries for
- transactional <literal>InnoDB</literal> tables that have been
- changed are invalidated when a <literal>COMMIT</literal> is
- performed.
+ Cache entries for transactional <literal>InnoDB</literal> tables
+ that have been changed are invalidated when a
+ <literal>COMMIT</literal> is performed.
</para>
<para>
@@ -27418,13 +27417,13 @@
</para>
<para>
- When a query is to be cached, its result (the data sent to
- the client) is stored in the query cache during result
- retrieval. Therefore the data usually is not handled in one big
- chunk. The query cache allocates blocks for storing this data on
- demand, so when one block is filled, a new block is allocated.
- Because memory allocation operation is costly (timewise), the
- query cache allocates blocks with a minimum size given by the
+ When a query is to be cached, its result (the data sent to the
+ client) is stored in the query cache during result retrieval.
+ Therefore the data usually is not handled in one big chunk. The
+ query cache allocates blocks for storing this data on demand, so
+ when one block is filled, a new block is allocated. Because
+ memory allocation operation is costly (timewise), the query
+ cache allocates blocks with a minimum size given by the
<literal>query_cache_min_res_unit</literal> system variable.
When a query is executed, the last result block is trimmed to
the actual data size so that unused memory is freed. Depending
Modified: trunk/refman-5.1/database-administration.xml
===================================================================
--- trunk/refman-5.1/database-administration.xml 2006-09-08 18:47:56 UTC (rev 3307)
+++ trunk/refman-5.1/database-administration.xml 2006-09-08 19:11:02 UTC (rev 3308)
Changed blocks: 1, Lines Added: 93, Lines Deleted: 0; 3621 bytes
@@ -14089,6 +14089,99 @@
<listitem>
<para>
+ <literal>CREATE INSTANCE
+ <replaceable>instance_name</replaceable>
+ [<replaceable>opt_name</replaceable>[=<replaceable>opt_val</replaceable>],
+ ...]</literal>
+ </para>
+
+ <para>
+ This command configures a new instance by creating an
+ <literal>[<replaceable>instance_name</replaceable>]</literal>
+ section in the configuration file. The section is empty if
+ no options are given. Otherwise, the options are added to
+ the section. Options should be given in the same format
+ used when you write options in option files, and separated
+ by commas. (See <xref linkend="option-files"/> for a
+ description of the allowable syntax.
+ </para>
+
+ <para>
+ For example, to create an instance section named
+ <literal>[mysqld98]</literal>, you might write something
+ like this in the configuration file:
+ </para>
+
+<programlisting>
+[mysqld98]
+basedir=/var/mysql98
+</programlisting>
+
+ <para>
+ To achieve this via <literal>CREATE INSTANCE</literal>,
+ issue this command to Instance Manager:
+ </para>
+
+<programlisting>
+mysql> <userinput>CREATE INSTANCE mysqld98 basedir=/var/mysql98;</userinput>
+Query OK, 0 rows affected (0,00 sec)
+</programlisting>
+
+ <para>
+ <literal>CREATE INSTANCE</literal> creates the instance
+ but does not start it.
+ </para>
+
+ <para>
+ The command fails if
+ <replaceable>instance_name</replaceable> is not a valid
+ instance name or the instance already exists.
+ </para>
+
+ <para>
+ If the instance name is the (deprecated) name
+ <literal>mysqld</literal>, the option list cannot include
+ any options that are specific to Instance Manager, such as
+ <literal>nonguarded</literal> (see
+ <xref linkend="instance-manager-configuration-files"/>).
+ </para>
+
+ <para>
+ This command was added in MySQL 5.1.12.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DROP INSTANCE
+ <replaceable>instance_name</replaceable></literal>
+ </para>
+
+ <para>
+ This command removes the configuration for
+ <replaceable>instance_name</replaceable> from the
+ configuration file.
+ </para>
+
+<programlisting>
+mysql> <userinput>DROP INSTANCE mysqld98;</userinput>
+Query OK, 0 rows affected (0,00 sec)
+</programlisting>
+
+ <para>
+ The command fails if
+ <replaceable>instance_name</replaceable> is not a valid
+ instance name, the instance does not exist, or is not
+ offline.
+ </para>
+
+ <para>
+ This command was added in MySQL 5.1.12.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
<literal>START INSTANCE
<replaceable>instance_name</replaceable></literal>
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r3308 - in trunk: refman-5.0 refman-5.1 | paul | 8 Sep |
