transaction log not reading in last transaction id on restart
Bug #659633 reported by
Joe Daly
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
if you start drizzled do a operation that will write to the transaction_log (create table) kill drizzled and then restart. The second startup event is given a transaction_id of 1 in the transaction_log rather then one higher then the last entry. So there are essentially two items with transaction_id equal to 1 in the log.
| tags: | added: replication |
Revision history for this message
| Joe Daly (skinny.moey) wrote | #1 |
| Changed in drizzle: | |
| status: | New → Invalid |
To post a comment you must log in.
we currently dont have a global id of any kind in the transaction log that survives any kind of restart so short of that the transaction_id being 1 is correct