Bug #44129 | MySQL don't write query in binlog | ||
---|---|---|---|
Submitted: | 7 Apr 2009 9:31 | Modified: | 7 Apr 2009 10:19 |
Reporter: | Alex Sheshenya | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.1.33 | OS: | Linux (Red Hat Enterprise Linux Server release 5.2 (Tikanga)) |
Assigned to: | CPU Architecture: | Any | |
Tags: | binlog, replication |
[7 Apr 2009 9:31]
Alex Sheshenya
[7 Apr 2009 9:40]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Please read at http://dev.mysql.com/doc/refman/5.1/en/binary-log.html: Evaluation of update selection options. The server evaluates the options for logging or ignoring updates to the binary log according to the following rules: ... # There are some rules (--binlog-do-db, --binlog-ignore-db, or both). Is there a default database (has any database been selected by USE?)? * No: Do not write the statement, and exit. * Yes: Go to the next step.
[7 Apr 2009 10:19]
Alex Sheshenya
Thanks. But I think if mysql allow query like database.table more rigt check query. If we use database.table query then use Yes: Go to the next step.