SpirirHost Support Centre: MySQL Reference Manual p.310

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

310 MySQL Technical Reference for Version 4.0.3 rm hostname-old.log Update logging is smart because it logs only statements that really update data. So an UPDATE or a DELETE with a WHERE that nds no rows is not written to the log. It even skips UPDATE statements that set a column to the value it already has. The update logging is done immediately after a query completes but before any locks are released or any commit is done. This ensures that the log will be logged in the execution order. If you want to update a database from update log les, you could do the following (assuming your update logs have names of the form `file_name.###'): shell> ls -1 -t -r file_name.[0-9]* | xargs cat | mysql ls is used to get all the log les in the right order. This can be useful if you have to revert to backup les after a crash and you want to redo the updates that occurred between the time of the backup and the crash. 4.9.4 The Binary Update Log The intention is that the binary log should replace the update log, so we recommend you to switch to this log format as soon as possible! The binary log contains all information that is available in the update log in a more ecient format. It also contains information about how long every query that updated the database took. The binary log is also used when you are replicating a slave from a master. See Section 4.10 [Replication], page 312. When started with the --log-bin[=file_name] option, mysqld writes a log le containing all SQL commands that update data. If no le name is given, it defaults to the name of the host machine followed by -bin. If le name is given, but it doesn't contain a path, the le is written in the data directory. If you supply an extension to --log-bin=filename.extension, the extension will be silenty removed. To the binary log lename mysqld will append an extension that is a number that is in- cremented each time you execute mysqladmin refresh, execute mysqladmin flush-logs, execute the FLUSH LOGS statement or restart the server. A new binary log will also au- tomatically be created when it reaches max_bin_log_size. You can delete all not active binary log les with the RESET MASTER command. See Section 4.5.4 [RESET], page 250. You can use the following options to mysqld to aect what is logged to the binary log: Option Description binlog-do-db=database_name Tells the master it should log updates for the specied database, and exclude all others not explicitly men- tioned. (Example: binlog-do-db=some_database) binlog-ignore-db=database_ name Tells the master that updates to the given database should not be logged to the binary log (Example: binlog-ignore-db=some_database)

MySQL Reference Manual

Home
Hosting Plans \| Domain Registration \| About Us \| Contact Us \| Site Map Terms of Use \| Privacy Policy \| Guarantees Merchant Accounts

SpiritHost - web hosting for spiritual and education sites SpiritHit.com - Religious and Spiritual Portal Copyright © 2002 Dyntex Group, Inc. All Rights Reserved

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide