Do not pass FLUSH or ANALYZE through replication stream
Bug #726741 reported by
David Shrewsbury
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Fix Released
|
High
|
David Shrewsbury | ||
| 7.0 |
Fix Released
|
High
|
David Shrewsbury | ||
Bug Description
These two commands are always passed through the replication stream with no way to NOT pass them through. This can cause problems on slaves (e.g., FLUSH TABLES WITH READ LOCK). They are also problematic in that any tables they reference need a schema specified in order to not break replication.
We will remove these from the replication stream for now until they can be handled properly.
Related branches
lp:~dshrews/drizzle/bug726741_block_flush_analyze
- Drizzle Developers: Pending requested
-
Diff: 29 lines (+0/-9)2 files modifieddrizzled/statement/analyze.cc (+0/-2)
drizzled/statement/flush.cc (+0/-7)
| tags: | added: replication |
| Changed in drizzle: | |
| assignee: | nobody → David Shrewsbury (dshrews) |
| status: | New → In Progress |
| milestone: | none → 2011-03-14 |
| importance: | Undecided → High |
To post a comment you must log in.
