List:General Discussion« Previous MessageNext Message »
From:BAUMEISTER Alexandre Date:April 3 2001 10:39am
Subject:Mysqld crashes with my DELETE query.
View as plain text  
Bonjour,

  I have a table created with :

CREATE TABLE intraday_PAR (
  symbole char(20) NOT NULL default '',
  date datetime NOT NULL default '0000-00-00 00:00:00',
  first double(17,5) NOT NULL default '0.00000',
  high double(17,5) NOT NULL default '0.00000',
  low double(17,5) NOT NULL default '0.00000',
  last double(17,5) NOT NULL default '0.00000',
  volume int(11) NOT NULL default '0',
  PRIMARY KEY  (symbole,date),
  KEY idx_symbole (symbole),
  KEY idx_date (date)
) TYPE=Innobase;

  There are about 400.000 rows in it :

mysql> select count(*) from intraday_PAR;
+----------+
| count(*) |
+----------+
|   379568 |
+----------+
1 row in set (0.86 sec)

  If  I  try  to  do  a  delete based on "date" (for which there is an
  index), it is really really long :

| 5 | root | localhost | cotations | Query | 255  | updating | delete from intraday_PAR
where date<'2001-04-03 00:00:00'

  Before mysqld crashes :
  
mysql> delete from intraday_PAR where date<'2001-04-03 00:00:00';
ERROR 2013: Lost connection to MySQL server during query


  And from the error log :

/usr/local/mysql/libexec/mysqld: ready for connections
mysqld got signal 11;
The manual section 'Debugging a MySQL server' tells you how to use a
stack trace and/or the core file to produce a readable backtrace that may
help in finding out why mysqld died.
010403 12:32:19  mysqld restarted
Innobase: Database was not shut down normally.
Innobase: Starting recovery from log files...
Innobase: Starting log scan based on checkpoint at
Innobase: log sequence number 0 487424247
Innobase: Doing recovery: scanned up to log sequence number 0 487489536
Innobase: Doing recovery: scanned up to log sequence number 0 487555072
Innobase: Doing recovery: scanned up to log sequence number 0 487600404
Innobase: 1 uncommitted transaction(s) which must be rolled back
Innobase: Starting rollback of uncommitted transactions
Innobase: Rolling back trx no 4045747
Innobase: Rolling back of trx no 4045747 completed
Innobase: Rollback of uncommitted transactions completed
Innobase: Starting an apply batch of log records to the database...
Innobase: Apply batch completed
Innobase: Started
/usr/local/mysql/libexec/mysqld: ready for connections


  Regards,
  Alex.


Thread
[couldn't connect to the mysql server]ujwol3 Apr
  • Re: [couldn't connect to the mysql server]James Lyon3 Apr
  • Re: [couldn't connect to the mysql server]Ujwol3 Apr
    • Re[2]: [couldn't connect to the mysql server]role+mysql-readers3 Apr
    • Mysqld crashes with my DELETE query.BAUMEISTER Alexandre3 Apr
      • Re: Mysqld crashes with my DELETE query.Bob Hall3 Apr
    • Mysqld crashes with my DELETE query.BAUMEISTER Alexandre3 Apr
  • Re: Re[2]: [couldn't connect to the mysql server]Ujwol3 Apr
Re: Mysqld crashes with my DELETE query.Heikki Tuuri3 Apr