Re: Problem with MySQL 4.0.14 - Server Crash
[EMAIL PROTECTED] wrote: I upgrade try to upgrade from MySQL 4.0.12 to 4.0.14 in Linux but it doesn't work. MySQL always crashs with error 11 Segmentation fault. I don't know why but I try to dump database (about 200,000 lines) and install MySQL 4.0.14 windows version and try to import database again to MySQL windows version. Nothing change database server crash. Then I downgrade to MySQL 3.23.55 (windows). There is no any problem, import work fine. Then I try to use MySQL 4.0.12 (windows), there is no problem again. I try to upgrade my Linux server to MySQL 4.0.13. The result is same as MySQL 4.0.14. Then I try to find which Query is crash. And know that MySQL 4.0.14 (Windows) always crashs when try to read field that include blank value in key (primary, index, unique) even MyISAM or InnoDB, server will crash. This bug is fixed in v4.0.15. * Fixed crash in comparisons of strings using the tis620 character set. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem with MySQL 4.0.14 - Server Crash
Hi! On Sep 10, Victoria Reznichenko wrote: [EMAIL PROTECTED] wrote: I upgrade try to upgrade from MySQL 4.0.12 to 4.0.14 in Linux but it doesn't work. MySQL always crashs with error 11 Segmentation fault. I don't know why but I try to dump database (about 200,000 lines) and install MySQL 4.0.14 windows version and try to import database again to MySQL windows version. Nothing change database server crash. Then I downgrade to MySQL 3.23.55 (windows). There is no any problem, import work fine. Then I try to use MySQL 4.0.12 (windows), there is no problem again. I try to upgrade my Linux server to MySQL 4.0.13. The result is same as MySQL 4.0.14. Then I try to find which Query is crash. And know that MySQL 4.0.14 (Windows) always crashs when try to read field that include blank value in key (primary, index, unique) even MyISAM or InnoDB, server will crash. This bug is fixed in v4.0.15. * Fixed crash in comparisons of strings using the tis620 character set. Vita, why do you think that this bugfix is relevant ? How do you know he is using tis620 charset - was it in some other email ? Regards, Sergei -- __ ___ ___ __ / |/ /_ __/ __/ __ \/ / Sergei Golubchik [EMAIL PROTECTED] / /|_/ / // /\ \/ /_/ / /__ MySQL AB, Senior Software Developer /_/ /_/\_, /___/\___\_\___/ Osnabrueck, Germany ___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Problem with MySQL 4.0.14 - Server Crash
Victoria, Thanks. -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Problem with MySQL 4.0.14 - Server Crash
I upgrade try to upgrade from MySQL 4.0.12 to 4.0.14 in Linux but it doesn't work. MySQL always crashs with error 11 Segmentation fault. I don't know why but I try to dump database (about 200,000 lines) and install MySQL 4.0.14 windows version and try to import database again to MySQL windows version. Nothing change database server crash. Then I downgrade to MySQL 3.23.55 (windows). There is no any problem, import work fine. Then I try to use MySQL 4.0.12 (windows), there is no problem again. I try to upgrade my Linux server to MySQL 4.0.13. The result is same as MySQL 4.0.14. Then I try to find which Query is crash. And know that MySQL 4.0.14 (Windows) always crashs when try to read field that include blank value in key (primary, index, unique) even MyISAM or InnoDB, server will crash. Try following query ---[CUT BEGIN]-- CREATE TABLE `temp` ( `a` VARCHAR( 100 ) NOT NULL , `b` VARCHAR( 50 ) NOT NULL , `c` VARCHAR( 50 ) NOT NULL , PRIMARY KEY ( `a` , `b` ) ); INSERT INTO `temp` ( `a` , `b` , `c` ) VALUES ( 'fadfasdf', '', 'asdf' ); SELECT * FROM `temp` WHERE `a` = 'fadfasdf' AND `b` = '' ---[CUT END]-- I test this query in my PC and notebook, it is same. Below is my.cnf ---[CUT BEGIN] [mysqld] port=3306 socket=MySQL default-character-set = tis620 skip-locking set-variable= key_buffer=4M set-variable= max_allowed_packet=1M set-variable= table_cache=64 set-variable= sort_buffer=512K set-variable= net_buffer_length=8K set-variable= myisam_sort_buffer_size=8M #server-id = 1 # Uncomment the following if you want to log updates #log-bin # Uncomment the following rows if you move the MySQL distribution to another # location basedir = c:/mysql/ datadir = c:/mysql/data/ # Uncomment the following if you are NOT using BDB tables skip-bdb #skip-innodb # Uncomment the following if you are using Innobase tables innodb_data_file_path = ibdata1:400M #innodb_data_home_dir = c:\mysql\ibdata #innodb_log_group_home_dir = c:\mysql\ibdata #innodb_log_arch_dir = c:\mysql\ibdata #set-variable = innodb_mirrored_log_groups=1 #set-variable = innodb_log_files_in_group=3 #set-variable = innodb_log_file_size=10M #set-variable = innodb_log_buffer_size=2M #innodb_flush_log_at_trx_commit=1 #innodb_log_archive=0 set-variable = innodb_buffer_pool_size=32M #set-variable = innodb_additional_mem_pool_size=2M #set-variable = innodb_file_io_threads=2 #set-variable = innodb_lock_wait_timeout=50 ---[CUT END]--- I must use default-character-set = tis620 because I store Thai text in database. If anyone have any suggestion, please help. -- __ Sign-up for your own personalized E-mail at Mail.com http://www.mail.com/?sr=signup CareerBuilder.com has over 400,000 jobs. Be smarter about your job search http://corp.mail.com/careers -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
