Hi!
I found the bug: memory was written over in the function which
estimates the number of rows in ha_innobase.cc.
The bug is fixed in version 3.23.36, which may be out today.
You can also fix the bug by editing ha_innobase.cc, about line 2460.
The last argument in the two calls to dict_index_c
gt;
Cc: "Arne Claassen" <[EMAIL PROTECTED]>; "Heikki Tuuri"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, March 26, 2001 4:05 PM
Subject: Re: Signal 11 on Innobase table range queries
>
> Hi!
>
> >>>>> "Jeremy" == Jeremy
Please unsubscribe me from the list.
-Original Message-
From: Michael Widenius [mailto:[EMAIL PROTECTED]]
Sent: Monday, March 26, 2001 10:35 AM
To: [EMAIL PROTECTED]
Cc: Arne Claassen; Heikki Tuuri; [EMAIL PROTECTED]
Subject: Re: Signal 11 on Innobase table range queries
Hi
Hi!
> "Jeremy" == Jeremy D Zawodny <[EMAIL PROTECTED]> writes:
Jeremy> On Sun, Mar 25, 2001 at 09:52:22PM -0800, Arne Claassen wrote:
>>
>> I've got a reproducable signal 11 death in mysqld using Innobase
>> tables and range queries (at least reproducable on my machine,
>> Redhat 6.2, mysq
On Sun, Mar 25, 2001 at 09:52:22PM -0800, Arne Claassen wrote:
>
> I've got a reproducable signal 11 death in mysqld using Innobase
> tables and range queries (at least reproducable on my machine,
> Redhat 6.2, mysql 3.23.35).
>
> Here's how it manifests itself: Create a table with at least 32
>
