Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
621ac0be
Commit
621ac0be
authored
Nov 25, 2009
by
Paul McCullagh
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Removed the assertion that assumes InnoDB is the only engine that supports XA
parent
6a8ec4a2
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
1 deletion
+6
-1
sql/handler.cc
sql/handler.cc
+6
-1
No files found.
sql/handler.cc
View file @
621ac0be
...
...
@@ -1588,7 +1588,12 @@ int ha_recover(HASH *commit_list)
for now, only InnoDB supports 2pc. It means we can always safely
rollback all pending transactions, without risking inconsistent data
*/
DBUG_ASSERT
(
total_ha_2pc
==
(
ulong
)
opt_bin_log
+
1
);
// only InnoDB and binlog
/* TODO: FIX THIS (2009-11-25)!
With PBXT 1.0.09 2 engines now support XA. For the moment I am just taking
out the assertion which fails because pbxt_xa_support is enabled by
default.
*/
//DBUG_ASSERT(total_ha_2pc == (ulong) opt_bin_log+1); // only InnoDB and binlog
tc_heuristic_recover
=
TC_HEURISTIC_RECOVER_ROLLBACK
;
// forcing ROLLBACK
info
.
dry_run
=
FALSE
;
#endif
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment