Bug #2222 | mysqldump -A -F creates new binlogs for each db dumped | ||
---|---|---|---|
Submitted: | 27 Dec 2003 9:54 | Modified: | 3 Feb 2004 10:52 |
Reporter: | Stefan Hinz | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: mysqldump Command-line Client | Severity: | S3 (Non-critical) |
Version: | 4.0.16 | OS: | Windows (Windows 2000) |
Assigned to: | Guilhem Bichot | CPU Architecture: | Any |
[27 Dec 2003 9:54]
Stefan Hinz
[30 Jan 2004 8:36]
Michael Widenius
I updated mysqldump --help to reflect the actual usage.
[3 Feb 2004 10:52]
Sergei Golubchik
The reason for flushing logs between databases is that mysqldump locks one database at time, so it has to flush logs per database to get a consistent snapshot. And it locks one database in time because 1. we don't want to make ALL tables read-only for the duration of the WHOLE backup 2. we don't want to open ALL tables at once (and LOCK TABLE opens it) because mysqld can simply get short of file descriptors and it's slow.