I have finished a script that takes the bit keeper sources and makes
MySQL-4.0.2 RPMS for Redhat 6.x and apparently 7.X as well. I can put these
up on our site for download if you want. They might get others trying the
code out.
I use the spec file included with the source code.
I'll put it up
That would be great. Thanks!
Sincerely,
Steven Roussey
http://Network54.com/?pp=e
-Original Message-
From: Brian P. Austin [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 12, 2002 10:45 pm
Subject: RE: Request for help in testing new replication code in 4.0.2
I have finished a
* If you want to do it this very moment, read the instructions at
http://www.mysql.com/doc/I/n/Installing_source_tree.html and install a
pre-release 4.0.2 MySQL on your test server. You may also wait until 4.0.2
is
released, but in that case, replication in 4.0.2 may have a bug you could
On Sat, Feb 09, 2002 at 09:41:25PM -0700, Sasha Pachev wrote:
Dear MySQL users,
I have just pushed my latest changes in the replication code in our
4.0 development tree, which change the slave to use two threads -
I/O thread that gets the data from the master and logs it, and SQL
thread
Hi,
In myisamchk.c replace the following line :
if (argument *argument == '0')
DBUG_POP();
else
DBUG_PUSH(argument ? argument : d:t:o,/tmp/myisamchk.trace);
by
if (argument *argument == '0')
{
DBUG_POP();
}
else
{
DBUG_PUSH(argument ?
Hi,
In myisamchk.c replace the following line :
if (argument *argument == '0')
DBUG_POP();
else
DBUG_PUSH(argument ? argument : d:t:o,/tmp/myisamchk.trace);
by
if (argument *argument == '0')
{
DBUG_POP();
}
else
{
DBUG_PUSH(argument ?
I don't actually see the error message in the output you sent. but I found a
similar problem yesterday and have the following work around:
= myisamchk.c 1.69 vs edited =
*** /tmp/myisamchk.c-1.69-20535 Thu Feb 7 17:21:33 2002
--- edited/myisamchk.c Sat Feb 9 22:48:57 2002
On Sat, Feb 09, 2002 at 09:41:25PM -0700, Sasha Pachev wrote:
So I need your help with field testing of my code. For those of you
who are wondering why you should - this will help us stabilize 4.0 a
lot of faster, and not only replication, but also the general SQL
features. So if you depend
* If you want to do it this very moment, read the instructions at
http://www.mysql.com/doc/I/n/Installing_source_tree.html and
install a
pre-release 4.0.2 MySQL on your test server. You may also wait until
4.0.2 is
released, but in that case, replication in 4.0.2 may have a bug you
It could also have been fixed by changing the:
DBUG_POP();
to:
DBUG_POP()
Notice the ; on the end effectively terminating the if statement.
Happy coding.
Chris
-Original Message-
From: Jeremy Zawodny [EMAIL PROTECTED]
[mailto:X]
Sent:
On Sunday 10 February 2002 01:17 am, you wrote:
I can't get it to start replicating.
Note, the master (db1.tias.com) is a 3.23 server. The slave is 4.0.2
(noritake.tias.com).
On the master I get:
mysql show master status;
On Sunday 10 February 2002 06:06 pm, Jeremy Zawodny wrote:
One question:
? Can you explain the relay log a bit. ?Does it shrink eventually? ?I
? see it growing and growing, so I don't know if the space is
? recycled, or if I need to do something to periodically flush the
? executed queries
On Sunday 10 February 2002 01:17 am, you wrote:
I can't get it to start replicating.
Note, the master (db1.tias.com) is a 3.23 server. The slave is 4.0.2
(noritake.tias.com).
On the master I get:
mysql show master status;
On Sunday 10 February 2002 02:20 pm, Jeremy Zawodny wrote:
I run `BUILD/compile-pentium --prefix=/home/mysql` and it fails after
several minutes. ?The output is large, so I've posted it here:
? http://public.yahoo.com/~jzawodn/mysql-build.log
(the good stuff is at the end, of course...)
* If you want to do it this very moment, read the instructions at
http://www.mysql.com/doc/I/n/Installing_source_tree.html and install a
pre-release 4.0.2 MySQL on your test server. You may also wait until 4.0.2
is
released, but in that case, replication in 4.0.2 may have a bug you could
On Sat, Feb 09, 2002 at 09:41:25PM -0700, Sasha Pachev wrote:
Dear MySQL users,
I have just pushed my latest changes in the replication code in our
4.0 development tree, which change the slave to use two threads -
I/O thread that gets the data from the master and logs it, and SQL
thread
Hi,
In myisamchk.c replace the following line :
if (argument *argument == '0')
DBUG_POP();
else
DBUG_PUSH(argument ? argument : d:t:o,/tmp/myisamchk.trace);
by
if (argument *argument == '0')
{
DBUG_POP();
}
else
{
DBUG_PUSH(argument ?
I don't actually see the error message in the output you sent. but I found a
similar problem yesterday and have the following work around:
= myisamchk.c 1.69 vs edited =
*** /tmp/myisamchk.c-1.69-20535 Thu Feb 7 17:21:33 2002
--- edited/myisamchk.c Sat Feb 9 22:48:57 2002
On Sat, Feb 09, 2002 at 09:41:25PM -0700, Sasha Pachev wrote:
So I need your help with field testing of my code. For those of you
who are wondering why you should - this will help us stabilize 4.0 a
lot of faster, and not only replication, but also the general SQL
features. So if you depend
19 matches
Mail list logo
