Correct, that error means "no more room in index file".
So, how do I get more room in the index file?
Paul DuBois wrote:
At 15:11 -0500 10/22/02, Chris Stoughton wrote:
I have 760 GB free, not 375.
Perhaps, but error 136 still means "no more room in index file".
build the index file, so it's possible you run out
of free space during the MYI generation ? (what does df report ? )
Regards,
Jocelyn
- Original Message -----
From: "Chris Stoughton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 22, 2002 9:49 P
I have tried a few different variables to allow a "create index" command
to finish successfully.
1. I set tmpdir to be a file system with ample space
2. I increased tmp_table_size
3. I increases myisam_sort_buffer_size to 100M
Here are the sizes of the database files:
bash-2.04$ ls -l target
136
136 = No more room in index file
Are you sure your file system can handle the size of your index
file ?
Regards,
Jocelyn
- Original Message -
From: "Chris Stoughton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 22, 2002 12:26 AM
Subject:
I am running 3.23.52-Max under Linux.
I now have a table with 54M rows:
mysql> select count(*) from targetTsObj;
+--+
| count(*) |
+--+
| 54549046 |
+--+
1 row in set (0.05 sec)
Creating an index on this takes 1 hour 10 minutes, with this error:
mysql> create index targ
It sounds like the glibc auto-rpm that Redhat produced (to plug a
security hole, I believe) is the root cause. Getting mysql 3.23.52 from
mysql will be the solution.
I don't know who could get Redhat to coordinate their updates.
John Hinton wrote:
>I'm having the same problems. I'm on a Red
I sent a similar question a few days ago. I don't think there was a
response. If there was, sorry that I missed it. I have worked around
the issue, but would like to know whether there is something I can do to
improve the orignal query.
I have a table with two spatial indices -- ra and decl
We found the same thing, after installing the glibc auto-rpm from Redhat.
The updated glibc packages from Red Hat will whack your
/etc/nsswitch.conf file. That is, it will mess with the order of how
things are searched for.
We noticed this with mysql not being able resolve remote server IPs.
I do this with
select db;
show tables;
then parse through the result.
Niclas Hedhman wrote:
>On Wednesday 09 October 2002 21:43, Inbal Ovadia wrote:
>
>
>>Hi all,
>>There is a way to know if I have table x in my db?
>>Let's say some catalog tables that hold information about the db like
>
I have a database with a table called targetTsObj, and I want to perform
many queries from it, such as this one:
select run,rerun,camcol,field,id,ra,decl,r from targetTsObj where ra
between 255.84730673785904 and 256.31969326214096 and decl between
58.7494108 and 58.9577892
On
Yes, I increased this to 512M, as suggested in another answer, and the
perfomance improved dramatically. Thanks for the tip.
Jeremy Zawodny wrote:
>On Mon, Sep 23, 2002 at 07:25:17AM -0500, Chris Stoughton wrote:
>
>
>>Joseph,
>>
>>Thanks for the quick answer.
[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
There is NO SETTING for key_buffer_size -- what value do you suggest?
Thanks,
Chris
Joseph Bueno wrote:
> Chris Stoughton wrote:
>
>> I have a table with a few million rows, wth 633 columns. I want to
I have a table with a few million rows, wth 633 columns. I want to
create 10 inidices on this table, six single-column and four two-column
inidices. The database will be loaded once and remain static, and
queried many times. Please note that this is a "small" prototype for
the actual databa
13 matches
Mail list logo
