Hi Mark,
On Dec 26, 2009, at 3:40 AM, MARK CALLAGHAN wrote:
InnoDB fixed group commit in the InnoDB plugin. This performs as
expected when the binlog is disabled. This does not perform as I
expect when the binlog is enabled.
Is this a problem for PBXT?
PBXT is also affected by the lack of
#At lp:maria
2782 kniel...@knielsen-hq.org 2009-12-29 [merge]
Merge Sergey's fix for pbxt.join_nested.
modified:
mysql-test/suite/pbxt/r/join_nested.result
mysql-test/suite/pbxt/t/join_nested.test
=== modified file 'mysql-test/suite/pbxt/r/join_nested.result'
---
#At lp:maria
2783 kniel...@knielsen-hq.org 2009-12-29 [merge]
Merge PBXT fix from Paul.
modified:
storage/pbxt/ChangeLog
storage/pbxt/src/discover_xt.cc
storage/pbxt/src/ha_pbxt.cc
storage/pbxt/src/strutil_xt.cc
=== modified file
Michael Widenius mo...@askmonty.org writes:
=== modified file 'mysql-test/t/ctype_utf8.test'
--- a/mysql-test/t/ctype_utf8.test2009-01-26 21:19:13 +
+++ b/mysql-test/t/ctype_utf8.test2009-12-27 13:54:41 +
@@ -2,6 +2,15 @@
# Tests with the utf8 character set
#
+let
Paul McCullagh paul.mccull...@primebase.org writes:
All tests look good, so I have proposed the bug fix mentioned below
for merging:
lp:~paul-mccullagh/maria/maria-pbxt-1009g
Thanks! I have merged this into the MariaDB 5.1.41 release clone (will later
also be merged into main lp:maria).
-
At file:///Users/hakan/work/monty_program/mariadb-tools/
revno: 4
revision-id: ha...@askmonty.org-20091229134253-zdbgd0ym9m7cokii
parent: kniel...@knielsen-hq.org-20091218103524-nof6wfpuku60r9rn
committer: Hakan Kuecuekyilmaz
On Mon, Dec 28, 2009 at 9:20 AM, Sergei Golubchik ser...@pisem.net wrote:
Hi, MARK!
On Dec 25, MARK CALLAGHAN wrote:
InnoDB fixed group commit in the InnoDB plugin. This performs as
expected when the binlog is disabled. This does not perform as I
expect when the binlog is enabled.
The
Hi, Paul!
On Dec 29, Paul McCullagh wrote:
On Dec 26, 2009, at 3:40 AM, MARK CALLAGHAN wrote:
* InnoDB locks prepare_commit_mutex in the prepare step
What is the purpose of this lock?
As far as I understand (disclaimer!), it's purpose is to ensure that
commit records in the InnoDB
Hi, MARK!
On Dec 29, MARK CALLAGHAN wrote:
On Mon, Dec 28, 2009 at 9:20 AM, Sergei Golubchik ser...@pisem.net wrote:
trn1 start transaction; insert t1 select * from t2;
trn1 commit;
trn1 ... xa_prepare() ...
trn2 start transaction; insert t2 values (1); commit;
trn2
Hi, Hakan!
On Dec 29, Hakan Kuecuekyilmaz wrote:
At file:///Users/hakan/work/monty_program/mariadb-tools/
revno: 4
revision-id: ha...@askmonty.org-20091229134253-zdbgd0ym9m7cokii
parent:
On Tue, Dec 29, 2009 at 11:07 AM, Sergei Golubchik ser...@pisem.net wrote:
Hi, MARK!
On Dec 29, MARK CALLAGHAN wrote:
On Mon, Dec 28, 2009 at 9:20 AM, Sergei Golubchik ser...@pisem.net wrote:
trn1 start transaction; insert t1 select * from t2;
trn1 commit;
trn1 ... xa_prepare() ...
On Tue, Dec 29, 2009 at 11:23 AM, Sergei Golubchik ser...@pisem.net wrote:
Hi, Paul!
On Dec 29, Paul McCullagh wrote:
On Dec 26, 2009, at 3:40 AM, MARK CALLAGHAN wrote:
* InnoDB locks prepare_commit_mutex in the prepare step
What is the purpose of this lock?
As far as I understand
12 matches
Mail list logo
