Sasha Pachev wrote:
So all I have to do, using the binary, is to take the mysqld file and
replace my old one (from 4.1.3 to 4.1.7, for example).
And for the source, I compile in another directory, then take the
mysqld file and replace my old one?
Is that documented somewhere?
Do not forget to
So all I have to do, using the binary, is to take the mysqld file and
replace my old one (from 4.1.3 to 4.1.7, for example).
And for the source, I compile in another directory, then take the mysqld
file and replace my old one?
Is that documented somewhere?
Do not forget to replace errmsg.sys
Sasha Pachev wrote:
It can be even simpler than that, if you stay withing the same
branch. Just replace mysqld and share/english/errmsg.sys ( or
share//errmsg.sys if you want them in your native
language) with the files from the new version.
This is for the source, binary or both? Sorry to as
It can be even simpler than that, if you stay withing the same branch.
Just replace mysqld and share/english/errmsg.sys ( or share//errmsg.sys if you want them in your native language) with
the files from the new version.
This is for the source, binary or both? Sorry to ask stupid questions,
Sasha Pachev wrote:
I did compile it from source, with the flags used for the binaries,
and now it does work. I'm totally confused now.
Is it easy to upgrade from source? With the binary, I could have two
separate directories and I would symlink the one I tested (most recent
version) and cou
I did compile it from source, with the flags used for the binaries, and
now it does work. I'm totally confused now.
Is it easy to upgrade from source? With the binary, I could have two
separate directories and I would symlink the one I tested (most recent
version) and could get back to the e
Sasha Pachev wrote:
Ugo Bellavance wrote:
Sasha Pachev wrote:
I tested the memory and it seems ok.
I doubt this is an hardware issue, since version 4.1.3 works perfectly.
Ugo:
Do the production and the test server run on the same hardware?
One is a single Athlon XP, the other is a dual Athlon M
Ugo Bellavance wrote:
Sasha Pachev wrote:
I tested the memory and it seems ok.
I doubt this is an hardware issue, since version 4.1.3 works perfectly.
Ugo:
Do the production and the test server run on the same hardware?
One is a single Athlon XP, the other is a dual Athlon MP.
Are you using the
Sasha Pachev wrote:
I tested the memory and it seems ok.
I doubt this is an hardware issue, since version 4.1.3 works perfectly.
Ugo:
Do the production and the test server run on the same hardware?
One is a single Athlon XP, the other is a dual Athlon MP.
Are you using the same mysqld binary on b
I tested the memory and it seems ok.
I doubt this is an hardware issue, since version 4.1.3 works perfectly.
Ugo:
Do the production and the test server run on the same hardware?
Are you using the same mysqld binary on both?
What I am suspecting is that the binary on the production system does has
Heikki Tuuri wrote:
Ugo,
- Original Message - From: "Ugo Bellavance" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, November 05, 2004 3:42 PM
Subject: Re: 4.1.7 serious problems
Gleb Paharenko wrote:
Hi.
There were several posts in list like yours.
D
; To: [EMAIL PROTECTED]
> Subject: Re: 4.1.7 serious problems
>
> Ugo,
>
> - Original Message -
> From: "Ugo Bellavance" <[EMAIL PROTECTED]>
> Newsgroups: mailing.database.myodbc
> Sent: Friday, November 05, 2004 3:42 PM
> Subject: Re: 4.1.7 s
Ugo,
- Original Message -
From: "Ugo Bellavance" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Friday, November 05, 2004 3:42 PM
Subject: Re: 4.1.7 serious problems
Gleb Paharenko wrote:
Hi.
There were several posts in list like yours.
Do you use InnoD
Gleb Paharenko wrote:
Hi.
There were several posts in list like yours.
Do you use InnoDB tables? Try to increase values
of key_buffer_size, read_buffer_size and so on.
InnoDB is enabled but no InnoDB table is used yet (coming soon).
However, it crashes with only 1 client connected. There is stil
Hi.
There were several posts in list like yours.
Do you use InnoDB tables? Try to increase values
of key_buffer_size, read_buffer_size and so on.
Ugo Bellavance <[EMAIL PROTECTED]> wrote:
> Hi,
>
>I've upgraded one of my servers (test) to 4.1.7 this week, all went ok.
> Now I
Anders Green wrote:
There are differences, starting with 4.1.5, with the
user/schema administration, that need to be updated/massaged.
Perhaps that is your problem?
I don't think so, everything works perfectly on my test server, which is
very similar.
Thanks,
Maybe.
:)
Anders
+===
There are differences, starting with 4.1.5, with the
user/schema administration, that need to be updated/massaged.
Perhaps that is your problem?
Maybe.
:)
Anders
+===+
|Anders Green Email: [EMAIL PROTECTED] |
|
Hi,
I've upgraded one of my servers (test) to 4.1.7 this week, all went ok.
Now I'm trying to upgrade another server (production) from 4.1.3 to
4.1.7 and I'm having serious problems. I tried 4.1.6 as well, same problem.
OS: Tao Linux (Red Hat Enterprise Linux 3.0 clone).
First, since I could
18 matches
Mail list logo
