holland-backup

Treat federated tables as transactional

Bug #1081261 reported by MikeG
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
holland-backup
Fix Committed
High
Andrew Garner
holland-backup 1.0.12

Bug Description

As mysqldump does not export rows for FEDERATED tables, we should avoid locking a database just because it has a table of this type. I believe that Holland currently treats view in this way (as well as innodb)

Revision history for this message
MikeG (mikegriffin) wrote :

I am unsure whether to treat federatedx tables this way.

Revision history for this message
MikeG (mikegriffin) wrote :

I see that federatedx has actually replaced federated on MariaDB so we couldn't treat it differently than federated anyway. This also means that the rows are not dumped (and the master ignores the locks)

Revision history for this message
Andrew Garner (muzazzi) wrote :

I agree. In the amsterdam branch I had parameterized the lock-method=autodetect logic to allow flagging engines, databases and individual tables as transactional. This is definitely on the roadmap.

Andrew Garner (muzazzi)
Changed in holland-backup:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Andrew Garner (muzazzi)
milestone: none → 1.0.10
Andrew Garner (muzazzi)
Changed in holland-backup:
milestone: 1.0.10 → 1.0.12
Andrew Garner (muzazzi)
Changed in holland-backup:
milestone: none → 1.0.12
Revision history for this message
Andrew Garner (muzazzi) wrote :

Feature branch here: https://github.com/holland-backup/holland/tree/feature/lp_1081261_federated_as_transactional

Should be included in holland 1.0.12

Andrew Garner (muzazzi)
Changed in holland-backup:
status: Triaged → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.