Oracle 5.0 Reference Manual page 2996

001207 22:07:56 bdb:
• Do not execute
ALTER TABLE
transactions until all those transactions complete. (The transaction might be ignored.)
•
ANALYZE TABLE, OPTIMIZE
you are using
INSERT
• Performing
LOCK TABLE ...
finished transaction in progress on the table.
• tables are relatively slow to open. If you have many
BDB
time to use the
mysql
rehash. This is especially noticeable when you have a large table cache.
• Replication uses query-level logging: The master writes the executed queries to the binary log. This
is a very fast, compact, and efficient logging method that works perfectly in most cases.
It is possible for the data on the master and slave to become different if a query is designed in such
a way that the data modification is nondeterministic (generally not a recommended practice, even
outside of replication).
For example:
•
CREATE TABLE ... SELECT
values into an
AUTO_INCREMENT
• if you are deleting rows from a table that has foreign keys with
DELETE
properties.
•
REPLACE ... SELECT,
inserted data.
If and only if the preceding queries have no
order.
For example, for
INSERT ... SELECT
different order (which results in a row having different ranks, hence getting a different number in the
column), depending on the choices made by the optimizers on the master and
AUTO_INCREMENT
slave.
A query is optimized differently on the master and slave only if:
• The table is stored using a different storage engine on the master than on the slave. (It is possible
to use different storage engines on the master and slave. For example, you can use
the master, but
MyISAM
• MySQL buffer sizes
• The master and slave run different MySQL versions, and the optimizer code differs between these
versions.
This problem may also affect database restoration using mysqlbinlog|mysql.
The easiest way to avoid this problem is to add an
nondeterministic queries to ensure that the rows are always stored or modified in the same order.
• Log file names are based on the server host name if you do not specify a file name with the startup
option. To retain the same log file names if you change your host name to something else, you must
explicitly use options such as
Command Options". Alternatively, rename the old files to reflect your host name change. If these are
Known Issues in MySQL
log_flush: LSN past current end-of-log
on a table on which you are running multiple-statement
BDB
TABLE, and
REPAIR TABLE
DELAYED.
and
FLUSH TABLES ...
client on the database if you are not using the
or
INSERT ... SELECT
column.
INSERT IGNORE ... SELECT
with no
on the slave if the slave has less available disk space.)
(key_buffer_size [458], and so on) are different on the master and slave.
--log-bin=old_host_name-bin
2976
may cause problems on tables for which
does not guarantee that there isn't a half-
tables in a database, it takes a long
BDB
-A
statements that insert zero or
if you have duplicate key values in the
clause guaranteeing a deterministic
ORDER BY
BY, the
ORDER SELECT
clause to the aforementioned
ORDER BY
[1467]. See
option or if you are using
NULL
ON DELETE CASCADE
may return rows in a
InnoDB
Section 5.1.3, "Server
on