I am not a coder, but I can probably help anyways for development.
I have CentOS systems at work which I can happily run tests against with
large real-world data. They are development systems I can trash.
i can't change CentOS that easily (maybe I can use virtual machines), but I
can put whatever v
Michael Widenius writes:
> knielsen> +++ b/sql/log.cc2010-10-04 10:48:08 +
> knielsen> @@ -6531,6 +6531,39 @@ err1:
> knielsen>"--tc-heuristic-recover={commit|rollback}");
> knielsen>return 1;
> knielsen> }
> knielsen> +
> knielsen> +static TC_LOG *
> knielsen> +t
Hi!
> "knielsen" == knielsen writes:
knielsen> At http://bazaar.launchpad.net/~maria-captains/maria/5.1
knielsen>
knielsen> revno: 2851
knielsen> revision-id: kniel...@knielsen-hq.org-20101004104808-asb7wcxoeg417j7d
knielsen> pare
Paul McCullagh writes:
> Hi Kristian,
Hi Paul, thanks for your detailed answer!
> I was a bit difficult to explain, so please ask if anything is not
> clear.
It seems pretty clear from your explanation. I will take a look into the
sources, and will let you know if I have any questions.
> With
Hi Philip,
On Mon, Sep 27, 2010 at 08:17:57PM +0300, Philip Stoev wrote:
> I have now managed to make buildbot produce automatic LCOV reports for
> MariaDB. You can view them here
>
> http://fedora13.selfip.org/lcov/
I looked, and noticed a problem: this coverage generator ignores markup
like '
This is something I'm always interested in. It seems most of us
understand where we need to go, but we don't know yet how to get
there... How do we convince Mark/Mark's boss that this is the best way
to develop MySQL codebase also from Facebook's point of view? (long
term we can make much bigger ad
Hi Kristian,
The easiest way to do this would be to add a parameter to
xn_end_xact() that indicates that the log should not be written or
flushed.
In xn_end_xact(), the last parameter to the call to xt_xlog_log_data()
determines what should happen:
#define XT_XLOG_NO_WRITE_NO_FLUSH
7 matches
Mail list logo
