Matthew J. Francis writes:
> On Thu, 2002-10-10 at 13:23, Sinisa Milivojevic wrote:
>
> I've pulled the latest 3.23 code with BK and compiled it on the machine
> in question. Unfortunately the problem still seems to be there as I can
> still knock the server over with the test case I wrote. The b
On Thu, 2002-10-10 at 13:23, Sinisa Milivojevic wrote:
>
> Hi!
>
> Our replication developers have recently fixed a bug that looks
> conspiciously like the one you reported.
>
> It will come up in 3.23.53 which should come up in 7 - 10 days.
>
> Would you please be so kind to check it out if
Hi!
Our replication developers have recently fixed a bug that looks
conspiciously like the one you reported.
It will come up in 3.23.53 which should come up in 7 - 10 days.
Would you please be so kind to check it out if it still persists.
If you would like to test code sooner, you can fetch
Matthew,
Wednesday, October 02, 2002, 5:29:38 PM, you wrote:
MJF> My company runs a moderately large and loaded MySQL replication network
MJF> across four Solaris machines. While upgrading from a fairly old 3.23.4x
MJF> installation to 3.23.52 we've encountered a problem with replication and
MJF>
Hi,
My company runs a moderately large and loaded MySQL replication network
across four Solaris machines. While upgrading from a fairly old 3.23.4x
installation to 3.23.52 we've encountered a problem with replication and
binlog rotation.
One of the machines is simultaneously slave to one server a
