I realized that I was using an older version of libmysqlclient. So I recompiled and
linked the msql-mysql-modules against mysql-3.23.41...
Bill Adams wrote:
> o If there is no call to 'flush tables', even a small data load will cause
> myisamcheck to report "warning: 1 clients is using or hasn
Bill Adams wrote:
> Spoiler: You may be right about the bad libs...
[snip]
> *** OMG ***
> But haha I cannot believe this, I was just looking at the libraries linked by
> mysqld with ldd and it is using the informix libpthread.so. Hmm, crap. *me
> slaps head*
Small Update:
o If there is no c
Spoiler: You may be right about the bad libs...
Kyle Hayes wrote:
> On Thursday 18 October 2001 12:31, Bill Adams wrote:
> Hmm, 2.2 doesn't do SMP really well. However, its drawbacks are limited to
> underuse of the CPUs rather than any kind of corruption or other issue. You
> would get much
On Thu, 18 Oct 2001, Kyle Hayes wrote:
> On Thursday 18 October 2001 09:45, Bill Adams wrote:
> > Matthew Bloch wrote:
> > > I'm running several MySQL installation (all version 3.23.37 under Linux)
> > > under what I presume are some fairly harsh conditions, and wondered what
> > > circumstances
Hi Matthew,
We had a similar problem that caused us to need to run myisamchk much more
than we wanted to.
It turned out that MySQL was not being shutdown when Unix was.
Symptom: The MySQL server error log did NOT show normal shutdown messages.
Cause 1: The normal method of shutting down MySQL u
On Thursday 18 October 2001 12:31, Bill Adams wrote:
> Kyle Hayes wrote:
> > > I found yesterday (at the advice of this list) that adding an
> > > occasional call to "FLUSH TABLES" fixed my corruption problems. I
> > > would do that right before the disconnect or program exit.
> >
> > What kernel
Kyle Hayes wrote:
> > I found yesterday (at the advice of this list) that adding an occasional
> > call to "FLUSH TABLES" fixed my corruption problems. I would do that right
> > before the disconnect or program exit.
>
> What kernel are you using? Some of the 2.4 series have... odd... behavior
vice to other users about what OS versions are
the most stable.
Regards,
Heikki
>- Original Message -
>From: "Heikki Tuuri" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Thursday, October 18, 2001 12:53 PM
>Subject: RE: Frequently corrupt table
On Thursday 18 October 2001 09:45, Bill Adams wrote:
> Matthew Bloch wrote:
> > I'm running several MySQL installation (all version 3.23.37 under Linux)
> > under what I presume are some fairly harsh conditions, and wondered what
> > circumstances cause tables to be corrupted and need fixing with
hat I have experience table corruption has been with MS
(NT and 98) due to OS freezes and blue screens. --flush cured those.
- Original Message -
From: "Heikki Tuuri" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 18, 2001 12:53 PM
Subject: RE:
Hi!
>Well, for one, I believe that Slashdot uses InnoDB tables, which tend to
handle
>a little better under very high load.
>Steve Meyers
> -Original Message-
>> From: Matthew Bloch [mailto:[EMAIL PROTECTED]]
>> Sent: Thursday, October 18, 2001 3:34 AM> To: [EMAIL PROTECTED]
>> Cc: Peter
Matthew Bloch wrote:
> I'm running several MySQL installation (all version 3.23.37 under Linux)
> under what I presume are some fairly harsh conditions, and wondered what
> circumstances cause tables to be corrupted and need fixing with myisamchk.
> This is happening once every few days and it'
Well, for one, I believe that Slashdot uses InnoDB tables, which tend to handle a
little better under very high load.
Steve Meyers
> -Original Message-
> From: Matthew Bloch [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 18, 2001 3:34 AM
> To: [EMAIL PROTECTED]
> Cc: Peter Tapho
13 matches
Mail list logo
