MySQL Community Server 5.6.26 has been released
Dear MySQL users, MySQL Server 5.6.26, a new version of the popular Open Source Database Management System, has been released. MySQL 5.6.26 is recommended for use on production systems. For an overview of what's new in MySQL 5.6, please see http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6 are available both as a "full" installer and as a "web" installer. The full installer is significantly larger and comes bundled with the latest software releases available. This bundle makes it easy to download and configure a full server and development suite. The web installer doesn't come bundled with any actual products and instead relies on download-on-demand to fetch only the products you choose to install. This makes the initial download much smaller but increases install time as the individual products will need to be downloaded. For information on installing MySQL 5.6.26 on new servers or upgrading to MySQL 5.6.26 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.6/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc: https://wikis.oracle.com/display/mysql/Contributing The following section lists the changes in the MySQL 5.6 since the release of MySQL 5.6.25. It may also be viewed online at http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-26.html Enjoy! Changes in MySQL 5.6.26 (2015-07-24) This release adds support for Debian 8 and Ubuntu 15.04. * MySQL Enterprise Notes * Performance Schema Notes * Security Notes * Functionality Added or Changed * Bugs Fixed MySQL Enterprise Notes * MySQL Enterprise Edition incorporates these changes for MySQL Enterprise Firewall: + The firewall implements a DETECTING intrusion-detection mode. For accounts in this mode, the firewall detects suspicious statements and writes them to the error log but does not deny access. The new Firewall_access_suspicious status variable counts the number of such statements. The sp_set_firewall_mode() stored procedure now synchronizes between in-memory rules and those in persistent storage for DETECTING mode, just as it does for PROTECTING mode. + A new sp_reload_firewall_rules() stored procedure reloads the in-memory rules for a registered account from the rules stored in the mysql.firewall_whitelist table, providing better control over firewall operation for individual accounts. + A new mysql_firewall_flush_status() UDF resets firewall access-counter status variables. To upgrade MySQL Enterprise Firewall if you have a version installed from a previous release, first uninstall the old version. Then install the new version and register your firewall configuration again. For instructions, see Installing or Uninstalling MySQL Enterprise Firewall (http://dev.mysql.com/doc/refman/5.6/en/firewall-installa tion.html). Performance Schema Notes * Current-event timing now provides more information. Previously, while a wait, stage, or statement event was executing, the respective tables displayed the event with TIMER_START populated, but with TIMER_END and TIMER_WAIT as NULL: events_waits_current events_stages_current events_statements_current To make it possible to determine how how long a not-yet-completed event has been running, the timer columns now are set as follows: + TIMER_START is populated (unchanged from previous behavior) + TIMER_END is populated with the current timer value + TIMER_WAIT is populated with the time elapsed so far (TIMER_END − TIMER_START) To find events that have not yet completed (that is, have no END_EVENT_ID) and have taken longer than N picoseconds thus far, monitoring applications can use this expression in queries: WHERE END_EVENT_ID IS NULL AND TIMER_WAIT > N (Bug #75156, Bug #20889406) Security Notes * Security Fix: Due to the LogJam issue (https://weakdh.org/), OpenSSL has changed the Diffie-Hellman key length parameters for openssl-1.0.1n and up. OpenSSL has provided a detailed explanation at http://openssl.org/news/secadv_20150611.txt. To adopt this change in MySQL, the following modifications were made: + The key length used in vio/viosslfactories.c for creating Diffie-Hellman keys has been increased from 512 to 2,048 bits. + The linked Op
Re: MySQL 5.5 Slow performance to insert
Hi, Your INSEERquery status is "Copying to tmp table", this means fetching rows which has to be inserted is slow. You should tune SELECT statement in your insert query. Adding indexes and/or simplifying query and/or .. so on. ``` ---TRANSACTION 31D6D74, ACTIVE 27107 sec mysql tables in use 8, locked 8 7470 lock struct(s), heap size 801208, 849088 row lock(s) MySQL thread id 15361, OS thread handle 0x7fea5e5c2700, query id 2690080 10.180.17.252 root Copying to tmp table insert into CONFERENCIA_ENCALHE (data, preco_capa_informado, qtde, qtde_informada, chamada_encalhe_cota_id, controle_conferencia_encalhe_cota_id, movimento_estoque_id, movimento_estoque_cota_id, produto_edicao_id,juramentada) (select distinct data_recolhimento, pe.preco_previsto, mec.qtde, mec.qtde, cec.id, ccec.id, me.id, mec.id, mec.produto_edicao_id,0 from movimento_estoque_cota_memoria mec, movimento_estoque_memoria me, chamada_encalhe ce, chamada_encalhe_cota cec, controle_conferencia_encalhe cce, controle_conferencia_encalhe_cota ccec, produto_edicao pe where mec.tipo_movimento_id = ``` yoku0825, 2015-07-25 5:35 GMT+09:00 Camilo Vieira : > Hi, > > My MySQL server is performing very slow inserts. Does somebody could help > me to understand what's happening? > > mysql> show engine innodb status \G > *** 1. row *** > Type: InnoDB > Name: > Status: > = > 150724 17:40:28 INNODB MONITOR OUTPUT > = > Per second averages calculated from the last 1 seconds > - > BACKGROUND THREAD > - > srv_master_thread loops: 173967 1_second, 173966 sleeps, 17386 10_second, > 191 background, 191 flush > srv_master_thread log flush and writes: 174022 > -- > SEMAPHORES > -- > OS WAIT ARRAY INFO: reservation count 40941, signal count 55139 > Mutex spin waits 101247, rounds 886301, OS waits 24221 > RW-shared spins 29684, rounds 413636, OS waits 11014 > RW-excl spins 18765, rounds 257448, OS waits 5190 > Spin rounds per wait: 8.75 mutex, 13.93 RW-shared, 13.72 RW-excl > > LATEST FOREIGN KEY ERROR > > 150722 18:23:08 Transaction: > TRANSACTION 31AC5E3, ACTIVE 8 sec inserting > mysql tables in use 3, locked 3 > 826 lock struct(s), heap size 96696, 31241 row lock(s), undo log entries > 9932 > MySQL thread id 932, OS thread handle 0x7feaf0042700, query id 42396 > 10.180.17.252 root > insert into movimento_estoque_cota ( > ID,APROVADO_AUTOMATICAMENTE,DATA_APROVACAO,STATUS,DATA,DATA_CRIACAO,TIPO_MOVIMENTO_ID,USUARIO_ID, > QTDE,PRODUTO_EDICAO_ID,COTA_ID,ESTOQUE_PROD_COTA_ID,ORIGEM,APROVADOR_ID,LANCAMENTO_ID,status_estoque_financeiro, > PRECO_COM_DESCONTO,PRECO_VENDA,VALOR_DESCONTO,FORMA_COMERCIALIZACAO) > (select > ID,true,date(sysdate()),'APROVADO',DATA,date(sysdate()),TIPO_MOVIMENTO_ID,1, > QTDE,PRODUTO_EDICAO_ID,COTA_ID, > ESTOQUE_PROD_COTA_ID, > 'CARGA_INICIAL',1,LANCAMENTO_ID, > IF(STATUS_ESTOQUE_FINANCEIRO=1,'FINANCEIRO_PROCESSADO','FINANCEIRO_NAO_PROCESSADO'), > PRECO_COM_DESCONTO,PRECO_ > Foreign key constraint fails for table > `teste_historico`.`movimento_estoque_cota`: > , > CONSTRAINT `FK459444C362506D6B` FOREIGN KEY (`ESTOQUE_PROD_COTA_ID`) > REFERENCES `estoque_produto_cota` (`ID`) > Trying to add in child table, in index `FK459444C362506D6B` tuple: > DATA TUPLE: 2 fields; > 0: len 8; hex 80054211; asc B ;; > 1: len 8; hex 8009743f; asc t?;; > > But in parent table `teste_historico`.`estoque_produto_cota`, in index > `PRIMARY`, > the closest match we can find is record: > PHYSICAL RECORD: n_fields 7; compact format; info bits 0 > 0: len 8; hex 80053f0d; asc ? ;; > 1: len 6; hex 031aba25; asc %;; > 2: len 7; hex 85561a1a14; ascV ;; > 3: len 9; hex 80; asc ;; > 4: len 9; hex 80003c; asc < ;; > 5: len 8; hex 8044; ascD;; > 6: len 8; hex 8001007d; asc};; > > > TRANSACTIONS > > Trx id counter 31DDD14 > Purge done for trx's n:o < 31D8A49 undo n:o < 0 > History list length 425 > LIST OF TRANSACTIONS FOR EACH SESSION: > ---TRANSACTION 0, not started > MySQL thread id 18036, OS thread handle 0x7fea5e591700, query id 2854409 > localhost root > show engine innodb status > ---TRANSACTION 31DDD13, not started > MySQL thread id 16024, OS thread handle 0x7fea5e4cd700, query id 2854407 > 10.129.28.111 root > ---TRANSACTION 31DC01D, not started > MySQL thread id 15932, OS thread handle 0x7fea5e52f700, query id 2812134 > 10.129.28.111 root > ---TRANSACTION 31D83B4, not started > MySQL thread id 15931, OS thread handle 0x7fea5d714700, query id 2721807 > 10.129.28.111 root > ---TRANSACTION 31D886C, not started > MySQL thread id 15930, OS thread handle 0x7fea5d776700, query id 2730189 > 10.129.28.111 root > ---TRANSACTION 31D8396, not started > MySQL thread id 15924, OS thread ha
