6 messages in com.mysql.lists.mysqlRe: Bizarre table type switch
FromSent OnAttachments
Stuart Felenstein28 Nov 2004 23:25 
Gleb Paharenko28 Nov 2004 23:55 
Stuart Felenstein28 Nov 2004 23:57 
Heikki Tuuri29 Nov 2004 11:01 
Stuart Felenstein29 Nov 2004 11:32 
Heikki Tuuri29 Nov 2004 13:52 
Subject:Re: Bizarre table type switch
From:Stuart Felenstein (stua@yahoo.com)
Date:11/29/2004 11:32:12 AM
List:com.mysql.lists.mysql

--- Heikki Tuuri <Heik@innodb.com> wrote:

Stuart,

you probably have

skip-innodb

in my.cnf.

Best regards,

Heikki Tuuri

Heikki - Nope , doesn't seem so. My.cnf is below. Also, I'm guessing that if it was set to skip-innodb, I wouldn't not have had the ability to change them back. It's very puzzling. I'm not expecting to find an answer. The logs were checked and nothing found to inidicate anything. I'm on shared host. Supposedly my ISP did this for me. They are pretty reliable. But we are talking about 20+ tables.

[mysqld] safe-show-database max_connections = 750 key_buffer = 136M myisam_sort_buffer_size = 72M join_buffer_size = 1M read_buffer_size = 1M sort_buffer_size = 2M table_cache = 1024 thread_cache_size = 128 wait_timeout = 5500 connect_timeout = 10 max_allowed_packet = 32M max_connect_errors = 10 query_cache_limit = 2M query_cache_size = 72M query_cache_type = 1 tmp_table_size = 72M read_rnd_buffer_size = 524288 bulk_insert_buffer_size = 72M

[mysqld_safe] open_files_limit = 8192

[mysqldump] quick max_allowed_packet = 32M

[myisamchk] key_buffer = 72M sort_buffer = 72M read_buffer = 24M write_buffer = 24M

Stuart