> Thank you very much for your bug report!
> And sorry if I doubted your report at the beginning; I hadn't thought
> of the rpm script.
No problem. I sometimes get bug reports that I know are impossible! Yet they
weren't. This one I would have barely noticed if it had not knocked the
slaves all of
> Hmm, I don't see any changes in ft-related files since 4.0.18 that could
> cause it (there were bugfixes, but they affect only *searching* - that
> is MATCH - and not *updating*).
>
> Can you create a test case ?
Well, I put up a file in the secret folder a few days ago as referenced in a
bug r
We start mysql with 'service mysql start' (we install from the RPM for
linux).
I've never seen mysql create binlog files under the name root before, and
after reverting to an old version, it doesn't again. It created a big mess
with all the slaves stuck at the end of an older binlog and not advanc
From: "Sergei Golubchik" <[EMAIL PROTECTED]>
> > 4. Thread stack warnings:
> >Warning: Asked for 196608 thread stack, but got 126976
> Same here.
OK, we can disable the warnings in the log file, but what's really behind
this warning?
A brand new, plain vanilla Fedora Core2 (aka RedHat FC2) ins
Hi!
On May 25, Steven Roussey wrote:
> We had some servers that were upgraded from 4.0.17/18 to 4.0.20 and had
> several problems thereafter:
>
> 1. Tables with FTS indices became corrupted, with queries on them causing
> segfaults on the servers.
Hmm, I don't see any changes in ft-related files
