Re: 64MB Limit on MyISAM indexes?

2001-04-23 Thread Ole Gjerde 

Hi,
I'm having that same problem, but I only have about 1.3 million rows in my
table, and the size is only about 190MB or so.

This started with 3.23.21 (Which had this problem, look in the changelog),
but it is also continuing after upgrading to 3.23.36.

I have a 3.23.36 slave that is replication off of the one above, and that
one now has a index that is well over 100MB.  Weird thing is that the db
files are 100% the same(ie, they are both from the same tar'ed mysql
directory/files), so this could suggest it has to do with glibc or somesuch.
The working on is a RH7(glibc 2.2) box and the non-working is an old
slackware 4.0(libc 5.4.46) box with some upgrades.

However, from the manual:
MySQL requires libc Version 5.4.12 or newer.  It's known to work with libc
5.4.46.

So that shouldn't be a problem either.

Both are running 2.2.19 on i386.

Thanks,
Ole Gjerde
Mimer AS

- Original Message -
From: ryc [EMAIL PROTECTED]
To: Jeff Brewer [EMAIL PROTECTED]; MySQL Mail List
[EMAIL PROTECTED]
Sent: Saturday, April 21, 2001 2:59 AM
Subject: Re: 64MB Limit on MyISAM indexes?


 You need to change the maxrows on the table. It is in the documentation,
I
 dont remember the exact syntax something like alter table tablename set
 maxrows=1 for tables larger than 2gigs.

 ryan

  I've got tables in ISAM format whose indexes are way over 64 MB.
However,
  when I try to create a MyISAM table with an index that big I get errors
 and
  confirming that with myisamchk I get:
 
  myisamchk: warning: Keyfile is almost full,   67107839 of   67107839
used
 
  Which is essentially 64MB.  Are MyISAM tables able to handle large
 indexes?
  I hope I don't have to go back to ISAM tables...



-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

3.23.36 index problem(error 136)

2001-04-20 Thread Ole Gjerde 

Hi,
We were running 3.23.21, which had the problem where the index file could
only go to 64MB.
So I shutdown the db, move the mysql directory(/usr/local/mysql) and
installed 3.23.36, and moved the database directories into the new version's
directory.  I then repaired the radacct table.

My problem is that the exact thing is happening with 3.23.36.  It gets up to
around 64MB and it stops(with table error 136):
-rw-r-   1 mysqlmysql67009536 Apr 20 14:00
/usr/local/mysql/var/radius/radacct.MYI

If I do a "REPAIR TABLE radacct QUICK", the index shrinks some and it works
again, but as soon as it gets back up to 67MB it stops working again with
the 136 error.

System has plenty of space so that's not a problem.

OS: Linux 2.2.19 on i386

Thanks for any help!
Ole Gjerde
Mimer AS


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail [EMAIL PROTECTED]
To unsubscribe, e-mail [EMAIL PROTECTED]
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php