Core Dump
Dear MySQL, Using 5.1.56, I have experienced this core dump. Is there anybody out there qualified to give an opinion on this? Many thanks, Ben Clewett. Thread pointer: 0x7fd5280dbd90 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x7fd51edf8100 thread_stack 0x4 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8b591e] /usr/sbin/mysqld(handle_segfault+0x351)[0x5e4ca1] /lib64/libpthread.so.0[0x7fda95f35a90] /usr/sbin/mysqld(my_hash_sort_simple+0x3d)[0x8c8a5d] /usr/sbin/mysqld(hp_hashnr+0x20a)[0x77b16a] /usr/sbin/mysqld(hp_search+0x66)[0x77c386] /usr/sbin/mysqld(heap_rnext+0x12f)[0x77eb9f] /usr/sbin/mysqld(_ZN7ha_heap10index_nextEPh+0x2d)[0x779fcd] /usr/sbin/mysqld(_ZN7handler15index_next_sameEPhPKhj+0x3a)[0x6d5e5a] /usr/sbin/mysqld(_ZN7handler21read_multi_range_nextEPP18st_key_multi_range+0x2f)[0x6d50af] /usr/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x14e)[0x6b73ae] /usr/sbin/mysqld[0x6d1246] /usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyyb+0x904)[0x67a994] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x36f7)[0x5f8a07] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x3d0)[0x5faec0] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x7b6)[0x5fb686] /usr/sbin/mysqld(_Z10do_commandP3THD+0xe6)[0x5fc716] /usr/sbin/mysqld(handle_one_connection+0x246)[0x5eed26] /lib64/libpthread.so.0[0x7fda95f2e070] /lib64/libc.so.6(clone+0x6d)[0x7fda953f213d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7fd521a122a0): is an invalid pointer Connection ID (thread ID): 47159998 Status: NOT_KILLED -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: MySQL version 3.23 to 5.x features
Assuming that your goal is to migrate an old database, perhaps the things that will bite you the fastest: * TYPE=MyISAM -- ENGINE=MyISAM. * CHARACTER SETs -- no concept in until 4.1. Use DEFAULT CHARACTER SET=latin1 for now. Later you can figure out how to migrate to utf8. (Note that 5.5 defaults to utf8, which is likely to dislike your bytes.) I would dump the data, then import into 5.x. Upgrading step by step would be quite tedious. Migration to InnoDB is also desirable, but not mandatory. -Original Message- From: Nagaraj S [mailto:nagaraj@gmail.com] Sent: Thursday, August 22, 2013 12:16 AM To: shawn green Cc: mysql@lists.mysql.com Subject: Re: MySQL version 3.23 to 5.x features wow it really helped me a lot. I really thank Shawn,Dale Jesper for there inputs On Wed, Aug 21, 2013 at 7:13 PM, shawn green shawn.l.gr...@oracle.comwrote: Hello Naga, On 8/21/2013 6:45 AM, Nagaraj S wrote: Hello, Can anyone share the features/comparison from MySQL version 3.23 to 5.x in single document? I can get from Google, however I have to navigate different pages/sites, if it is in single document that will be useful to see the overview of mysql features While not exactly just one single page for all changes, there is a single page of the fine manual within each new major version that describes the big features that are new or changed within that version. http://dev.mysql.com/doc/**refman/5.0/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.1/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.5/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html http://dev.mysql.com/doc/**refman/5.6/en/mysql-nutshell.**htmlhttp:// dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html Unfortunately, to learn what we changed between 3.23 - 4.0 or between 4.0 - 4.1, you are going to need to review the change logs http://dev.mysql.com/doc/**refman/4.1/en/news.htmlhttp://dev.mysql.co m/doc/refman/4.1/en/news.html from http://dev.mysql.com/doc/**refman/4.1/en/index.htmlhttp://dev.mysql.c om/doc/refman/4.1/en/index.html This manual describes features that are not included in every edition of MySQL 3.23, MySQL 4.0, and MySQL 4.1; such features may not be included in the edition of MySQL 3.23, MySQL 4.0, or MySQL 4.1; licensed to you. I can pretty much summarize the deficiencies in 3.23 like this * No InnoDB, Archive, CSV, Federated, or Blackhole storage engines * No table partitioning * No Views * No Stored Procedures or Stored Functions * No Triggers * No Events * Severe scalability limits (won't run as fast with reasonably concurrent loads even on great hardware as later versions) * Completely out of print (unpublished) and unsupported. * Missing literally thousands of bug fixes and performance improvements Any new project should be starting out with 5.6. Any production server should be on 5.5 or 5.6 by now or migrating soon. It is also a fairly safe bet that if you are still operating a 3.23 instance of MySQL that it is also time to upgrade your hardware. Regards, -- Shawn Green MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware and Software, Engineered to Work Together. Office: Blountville, TN -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
RE: Core Dump
bugs.mysql.com -Original Message- From: Ben Clewett [mailto:b...@clewett.org.uk] Sent: Thursday, September 05, 2013 6:38 AM To: mysql@lists.mysql.com Subject: Core Dump Dear MySQL, Using 5.1.56, I have experienced this core dump. Is there anybody out there qualified to give an opinion on this? Many thanks, Ben Clewett. Thread pointer: 0x7fd5280dbd90 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0x7fd51edf8100 thread_stack 0x4 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8b591e] /usr/sbin/mysqld(handle_segfault+0x351)[0x5e4ca1] /lib64/libpthread.so.0[0x7fda95f35a90] /usr/sbin/mysqld(my_hash_sort_simple+0x3d)[0x8c8a5d] /usr/sbin/mysqld(hp_hashnr+0x20a)[0x77b16a] /usr/sbin/mysqld(hp_search+0x66)[0x77c386] /usr/sbin/mysqld(heap_rnext+0x12f)[0x77eb9f] /usr/sbin/mysqld(_ZN7ha_heap10index_nextEPh+0x2d)[0x779fcd] /usr/sbin/mysqld(_ZN7handler15index_next_sameEPhPKhj+0x3a)[0x6d5e5a] /usr/sbin/mysqld(_ZN7handler21read_multi_range_nextEPP18st_key_multi_range +0x2f)[0x6d50af] /usr/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x14e)[0x6b73ae] /usr/sbin/mysqld[0x6d1246] /usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st _orderEyyb+0x904)[0x67a994] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x36f7)[0x5f8a07] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x3d0)[0x5faec0] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x7b6)[ 0x5fb686] /usr/sbin/mysqld(_Z10do_commandP3THD+0xe6)[0x5fc716] /usr/sbin/mysqld(handle_one_connection+0x246)[0x5eed26] /lib64/libpthread.so.0[0x7fda95f2e070] /lib64/libc.so.6(clone+0x6d)[0x7fda953f213d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7fd521a122a0): is an invalid pointer Connection ID (thread ID): 47159998 Status: NOT_KILLED -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
