Bug #9106 | MySQL coredumps on FreeBSD if the SQL query contains a regexp expression | ||
---|---|---|---|
Submitted: | 10 Mar 2005 20:47 | Modified: | 4 May 2005 18:36 |
Reporter: | Daniel Stefan Haischt | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Compiling | Severity: | S1 (Critical) |
Version: | mysql-5.0.2-alpha (FreeBSD port: mysql-c | OS: | FreeBSD (FreeBSD 5.4-PRERELEASE) |
Assigned to: | CPU Architecture: | Any |
[10 Mar 2005 20:47]
Daniel Stefan Haischt
[11 Mar 2005 23:35]
Jorge del Conde
Hi, Can you please provide us with the table schema for 'evo_posts' ? Thanks.
[11 Mar 2005 23:56]
Daniel Stefan Haischt
Below you'll find the original DDL that did create the table 'evo_posts': CREATE TABLE evo_posts ( ID int(10) unsigned NOT NULL auto_increment, post_author int(4) NOT NULL default '0', post_issue_date datetime NOT NULL default '0000-00-00 00:00:00', post_mod_date datetime NOT NULL default '0000-00-00 00:00:00', post_status enum('published','deprecated','protected','private','draft') NOT NULL default 'published', post_locale VARCHAR(20) NOT NULL DEFAULT 'en-EU', post_content text NOT NULL, post_title text NOT NULL, post_urltitle VARCHAR(50) NULL DEFAULT NULL, post_url VARCHAR(250) NULL DEFAULT NULL, post_category int(4) NOT NULL default '0', post_autobr tinyint(4) NOT NULL default '1', post_flags SET( 'pingsdone', 'imported'), post_karma int(11) NOT NULL default '0', post_wordcount int(11) default NULL, post_comments ENUM('disabled', 'open', 'closed') NOT NULL DEFAULT 'open', post_renderers VARCHAR(179) NOT NULL default 'default', PRIMARY KEY post_ID( ID ), INDEX post_issue_date( post_issue_date ), INDEX post_category( post_category ), INDEX post_author( post_author ), INDEX post_status( post_status ), UNIQUE post_urltitle( post_urltitle ) )
[12 Mar 2005 0:29]
Daniel Stefan Haischt
I kinda solved the issue: - Initially I did create the database 'b2e' using PhpMyAdmin. If using that database MySQL did coredump while using a select statement that did contain a REGEXP expression. - Today I did drop the b2e database as the user 'b2e' which owns that DB. After that I did re-create the database (create database b2e) as user 'b2e'. - Finally I did re-run the b2e installer and the core dump did not occure any more. No idea what's going on ... - At the very end I did figure out that I did create the very first DB using the following SQL statement 'CREATE DATABASE `b2e` DEFAULT CHARACTER SET utf8 COLLATE utf8_unicode_ci;' However using the statement 'CREATE DATABASE `b2e` DEFAULT CHARACTER SET latin1 COLLATE latin1_german1_ci;' does not cause a mysqld core dump. Anyway I would say MySQL shouldn't coredump if ... - there are issues with the REGEXP - there are issues with wrong database permissions - there is an issue with the character encoding
[14 Apr 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[15 Apr 2005 14:44]
Sergei Golubchik
reopened
[4 May 2005 18:36]
Hartmut Holzgraefe
verified with 5.0.2 on Linux, doesn't happen anymore with releases >=5.0.3