File not found

The link you requested was not found.

You can take a look at our whole site map, see if one of the search results below helps you, or try searching the site for the information you need.

1. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1.1 Replication and AUTO_INCREMENT

16.3.1.1. Replication and AUTO_INCREMENT Replication of AUTO_INCREMENT , LAST_INSERT_ID() , and TIMESTAMP values is done correctly, subject to the following exceptions. INSERT DELAYED ... VALUES(LAST_INSERT_ID()) inserts a different value on the master and the slave. ( Bug#20819 ) This is fixed in MySQL 5.1 when using row-based or mixed-format binary logging. Before MySQL 5.0.26, a stored procedure that uses LAST_INSERT_ID() does not replicate properly. When a statement uses a stored function that inserts i
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-auto-increment.html

2. MySQL :: MySQL 5.1 Reference Manual :: 16.3.1.1 Replication and AUTO_INCREMENT

16.3.1.1. Replication and AUTO_INCREMENT Replication of AUTO_INCREMENT , LAST_INSERT_ID() , and TIMESTAMP values is done correctly, subject to the following exceptions. A stored procedure that uses LAST_INSERT_ID() does not replicate properly using statement-based binary logging. This limitation is lifted in MySQL 5.1.12. Prior to MySQL 5.1.12, when a stored routine or trigger caused an INSERT into an AUTO_INCREMENT column, the generated AUTO_INCREMENT value was not written into the binary log, so a differe
» http://dev.mysql.com/doc/refman/5.1/en/replication-features-auto-increment.html

3. MySQL :: MySQL 5.0 Reference Manual :: 3.6.9 Using AUTO_INCREMENT

3.6.9. Using AUTO_INCREMENT The AUTO_INCREMENT attribute can be used to generate a unique identity for new rows: CREATE TABLE animals ( id MEDIUMINT NOT NULL AUTO_INCREMENT, name CHAR(30) NOT NULL, PRIMARY KEY (id) ); INSERT INTO animals (name) VALUES ('dog'),('cat'),('penguin'), ('lax'),('whale'),('ostrich'); SELECT * FROM animals; Which returns: +----+---------+ | id | name | +----+---------+ | 1 | dog | | 2 | cat | | 3 | penguin | | 4 | lax | | 5 | whale | | 6 | ostrich | +----+---------+ You can retriev
» http://dev.mysql.com/doc/refman/5.0/en/example-auto-increment.html

4. MySQL :: MySQL 5.1 with Maria Reference Manual :: 16.3.1.1 Replication and AUTO_INCREMENT

16.3.1.1. Replication and AUTO_INCREMENT Replication of AUTO_INCREMENT , LAST_INSERT_ID() , and TIMESTAMP values is done correctly, subject to the following exceptions. A stored procedure that uses LAST_INSERT_ID() does not replicate properly using statement-based binary logging. This limitation is lifted in MySQL 5.1.12. Prior to MySQL 5.1.12, when a stored routine or trigger caused an INSERT into an AUTO_INCREMENT column, the generated AUTO_INCREMENT value was not written into the binary log, so a differe
» http://dev.mysql.com/doc/refman/5.1-maria/en/replication-features-auto-increment.html

5. MySQL :: MySQL 5.0 Reference Manual :: 13.2.6.3 How AUTO_INCREMENT Handling Works in InnoDB

13.2.6.3. How AUTO_INCREMENT Handling Works in InnoDB If you specify an AUTO_INCREMENT column for an InnoDB table, the table handle in the InnoDB data dictionary contains a special counter called the auto-increment counter that is used in assigning new values for the column. This counter is stored only in main memory, not on disk. InnoDB uses the following algorithm to initialize the auto-increment counter for a table t that contains an AUTO_INCREMENT column named ai_col : After a server startup, for the fi
» http://dev.mysql.com/doc/refman/5.0/en/innodb-auto-increment-handling.html

6. MySQL :: MySQL 6.0 Reference Manual :: 16.3.1.1 Replication and AUTO_INCREMENT

16.3.1.1. Replication and AUTO_INCREMENT Replication of AUTO_INCREMENT , LAST_INSERT_ID() , and TIMESTAMP values is done correctly, subject to the following exceptions. An insert into an AUTO_INCREMENT column caused by a stored routine or trigger running on a master that uses MySQL 5.0.60 or earlier does not replicate correctly to a slave running MySQL 6.0 prior to 6.0.5. ( Bug#33029 ) Adding an AUTO_INCREMENT column to a table with ALTER TABLE might not produce the same ordering of the rows on the slave an
» http://dev.mysql.com/doc/refman/6.0/en/replication-features-auto-increment.html

7. MySQL :: MySQL 6.0 Reference Manual :: 13.5.6.3 How AUTO_INCREMENT Handling Works in InnoDB

13.5.6.3. How AUTO_INCREMENT Handling Works in InnoDB [ +/- ] 13.5.6.3.1. “ Traditional ” InnoDB Auto-Increment Locking 13.5.6.3.2. Configurable InnoDB Auto-Increment Locking InnoDB provides a locking strategy that significantly improves scalability and performance of SQL statements that add rows to tables with AUTO_INCREMENT columns. This section provides background information on the original (“ traditional ”) implementation of auto-increment locking in InnoDB , explains the configurable locking mechanism
» http://dev.mysql.com/doc/refman/6.0/en/innodb-auto-increment-handling.html

8. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1 Replication Features and Issues

16.3.1. Replication Features and Issues [ +/- ] 16.3.1.1. Replication and AUTO_INCREMENT 16.3.1.2. Replication and Character Sets 16.3.1.3. Replication DIRECTORY Statements 16.3.1.4. Replication with Floating-Point Values 16.3.1.5. Replication and FLUSH 16.3.1.6. Replication and Functions 16.3.1.7. Replication and LOAD ... Operations 16.3.1.8. Replication During a Master Crash 16.3.1.9. Replication During a Master Shutdown 16.3.1.10. Replication with MEMORY Tables 16.3.1.11. Replication and the Query Optimi
» http://dev.mysql.com/doc/refman/5.0/en/replication-features.html

9. MySQL :: MySQL 5.0 Reference Manual :: A.13 MySQL 5.0 FAQ — Replication

A.13. MySQL 5.0 FAQ — Replication For answers to common queries and question regarding Replication within MySQL, see Section 16.3.4, “Replication FAQ” .
» http://dev.mysql.com/doc/refman/5.0/en/faqs-replication.html

10. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1.4 Replication with Floating-Point Values

16.3.1.4. Replication with Floating-Point Values Floating-point values are approximate, so comparisons involving them are inexact. This is true for operations that use floating-point values explicitly, or values that are converted to floating-point implicitly. Comparisons of floating-point values might yield different results on master and slave servers due to differences in computer architecture, the compiler used to build MySQL, and so forth. See Section 11.2.2, “Type Conversion in Expression Evaluation”
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-floatvalues.html

11. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1.16 Replication Retries and Timeouts

16.3.1.16. Replication Retries and Timeouts In MySQL 5.0 (starting from 5.0.3), there is a global system variable slave_transaction_retries : If the replication slave SQL thread fails to execute a transaction because of an InnoDB deadlock or because it exceeded the InnoDB innodb_lock_wait_timeout or the NDBCluster TransactionDeadlockDetectionTimeout or TransactionInactiveTimeout value, the transaction automatically retries slave_transaction_retries times before stopping with an error. The default value is 1
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-timeouts.html

12. MySQL :: MySQL 5.1 Reference Manual :: 3.6.9 Using AUTO_INCREMENT

3.6.9. Using AUTO_INCREMENT The AUTO_INCREMENT attribute can be used to generate a unique identity for new rows: CREATE TABLE animals ( id MEDIUMINT NOT NULL AUTO_INCREMENT, name CHAR(30) NOT NULL, PRIMARY KEY (id) ); INSERT INTO animals (name) VALUES ('dog'),('cat'),('penguin'), ('lax'),('whale'),('ostrich'); SELECT * FROM animals; Which returns: +----+---------+ | id | name | +----+---------+ | 1 | dog | | 2 | cat | | 3 | penguin | | 4 | lax | | 5 | whale | | 6 | ostrich | +----+---------+ You can retriev
» http://dev.mysql.com/doc/refman/5.1/en/example-auto-increment.html

13. MySQL :: MySQL 5.1 with Maria Reference Manual :: 3.6.9 Using AUTO_INCREMENT

3.6.9. Using AUTO_INCREMENT The AUTO_INCREMENT attribute can be used to generate a unique identity for new rows: CREATE TABLE animals ( id MEDIUMINT NOT NULL AUTO_INCREMENT, name CHAR(30) NOT NULL, PRIMARY KEY (id) ); INSERT INTO animals (name) VALUES ('dog'),('cat'),('penguin'), ('lax'),('whale'),('ostrich'); SELECT * FROM animals; Which returns: +----+---------+ | id | name | +----+---------+ | 1 | dog | | 2 | cat | | 3 | penguin | | 4 | lax | | 5 | whale | | 6 | ostrich | +----+---------+ You can retriev
» http://dev.mysql.com/doc/refman/5.1-maria/en/example-auto-increment.html

14. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1.9 Replication During a Master Shutdown

16.3.1.9. Replication During a Master Shutdown It is safe to shut down a master server and restart it later. When a slave loses its connection to the master, the slave tries to reconnect immediately and retries periodically if that fails. The default is to retry every 60 seconds. This may be changed with the CHANGE MASTER TO statement or --master-connect-retry option. A slave also is able to deal with network connectivity outages. However, the slave notices the network outage only after receiving no data fr
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-mastershutdown.html

15. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1.14 Replication during a Slave Shutdown

16.3.1.14. Replication during a Slave Shutdown Shutting down the slave (cleanly) is also safe because it keeps track of where it left off. Unclean shutdowns might produce problems, especially if the disk cache was not flushed to disk before the system went down. Your system fault tolerance is greatly increased if you have a good uninterruptible power supply. Unclean shutdowns of the master may cause inconsistencies between the content of tables and the binary log in master; this can be avoided by using Inno
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-slaveshutdown.html

16. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1.5 Replication and FLUSH

16.3.1.5. Replication and FLUSH Some forms of the FLUSH statement are not logged because they could cause problems if replicated to a slave: FLUSH LOGS , FLUSH MASTER , FLUSH SLAVE , and FLUSH TABLES WITH READ LOCK . For a syntax example, see Section 12.5.5.2, “ FLUSH Syntax” . The FLUSH TABLES , ANALYZE TABLE , OPTIMIZE TABLE , and REPAIR TABLE statements are written to the binary log and thus replicated to slaves. This is not normally a problem because these statements do not modify table data. However, t
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-flush.html

17. MySQL :: MySQL 5.0 Reference Manual :: 16 Replication

Chapter 16. Replication Table of Contents       [ +/- ] 16.1. Replication Configuration       [ +/- ] 16.1.1. How to Set Up Replication 16.1.2. Replication Startup Options and Variables 16.1.3. Common Replication Administration Tasks 16.2. Replication Solutions       [ +/- ] 16.2.1. Using Replication for Backups 16.2.2. Using Replication with Different Master and Slave Storage Engines 16.2.3. Using Replication for Scale-Out 16.2.4. Replicating Different Databases to Different Slaves 16.2.5. Improving Replic
» http://dev.mysql.com/doc/refman/5.0/en/replication.html

18. MySQL :: MySQL 5.0 Reference Manual :: 16.1.1.1 Creating a User for Replication

16.1.1.1. Creating a User for Replication Each Slave must connect to the Master using a standard username and password. The user that you use for this operation can be any user, providing they have been granted the REPLICATION SLAVE privilege. You do not need to create a specific user for replication. However, you should be aware that the username and password will be stored in plain text within the master.info file. Therefore you may want to create a user that only has privileges for the replication proces
» http://dev.mysql.com/doc/refman/5.0/en/replication-howto-repuser.html

19. MySQL :: MySQL 5.0 Reference Manual :: 16.3.1.7 Replication and LOAD ... Operations

16.3.1.7. Replication and LOAD ... Operations Using LOAD TABLE FROM MASTER where the master is running MySQL 4.1 and the slave is running MySQL 5.0 may corrupt the table data, and is not supported. ( Bug#16261 ) The LOAD DATA INFILE statement's CONCURRENT option is not replicated; that is, LOAD DATA CONCURRENT INFILE is replicated as LOAD DATA INFILE , and LOAD DATA CONCURRENT LOCAL INFILE is replicated as LOAD DATA LOCAL INFILE . ( Bug#34628 ) The following applies only if either the master or the slave is
» http://dev.mysql.com/doc/refman/5.0/en/replication-features-load.html

20. MySQL :: MySQL 5.0 Reference Manual :: 16.4 Replication Implementation Overview

16.4. Replication Implementation Overview [ +/- ] 16.4.1. Replication Implementation Details 16.4.2. Replication Relay and Status Files 16.4.3. How Servers Evaluate Replication Rules MySQL replication is based on the master server keeping track of all changes to your databases (updates, deletes, and so on) in its binary logs. Therefore, to use replication, you must enable binary logging on the master server. See Section 5.2.3, “The Binary Log” . Each slave server receives from the master the saved updates t
» http://dev.mysql.com/doc/refman/5.0/en/replication-implementation.html

Can't find what you were looking for?