Bug #50512 | Bug in HOWTO causes don't work db replication | ||
---|---|---|---|
Submitted: | 21 Jan 2010 15:37 | Modified: | 25 Apr 2010 16:32 |
Reporter: | Brais Denís Devesa Cela | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.5 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | bin, bug, DB, how, log, replication, to |
[21 Jan 2010 15:37]
Brais Denís Devesa Cela
[22 Jan 2010 16:54]
Valeriy Kravchuk
Please, be more specific: where is the bug? You state that binlog-do-db=... MUST be added, but this is NOT true. This variable restricts binary logging, see http://dev.mysql.com/doc/refman/5.0/en/replication-options-binary-log.html#option_mysqld_b...: "Tell the server to restrict binary logging to updates for which the default database is db_name (that is, the database selected by USE). All other databases that are not explicitly mentioned are ignored. If you use this option, you should ensure that you do updates only in the default database." By default ALL updates are logged. So, explicit setting of binlog-do-db=... is NOT needed to setup master in general.
[22 Jan 2010 17:06]
Stefan Hinz
Changing to "Need Doc Info", because if it's a docs bug we need to know what to change in the docs.
[22 Jan 2010 20:31]
Brais Denís Devesa Cela
The problem is the "-", must remplaced by "_" or else don't works in this lines: log-bin====>log_bin, logbin-do-db====>logbin_do_db.
[23 Jan 2010 1:00]
Paul DuBois
That's not necessary. '-' and '_' are treated the same way in startup options. I don't see the bug here.
[23 Jan 2010 1:19]
Brais Denís Devesa Cela
With Ubuntu 8.04 and LAMP installed (all updated), if I write with "-" and not "_" it don't works, What can be the problem?
[25 Mar 2010 16:32]
Paul DuBois
The manual is correct. If you are experiencing a problem, please show what happens, including your exact configuration information and the error output you get as a result. Thanks.
[25 Apr 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".