複数の条件でクエリを実行すると、mysqlがクラッシュする

2つの条件でクエリを実行すると、mysqlのクラッシュが発生します。各条件でクエリを実行しても問題ありません。複数の条件でクエリを実行すると、mysqlがクラッシュする

MySQLバージョン：mysqlの-5.7.19-winx64

OS：Windows 7の究極の

誰もが、このバージョンのためにいくつかのアドバイスを与えることができますか？

PS：my.iniで質問を解決することは可能ですか？

テーブル：

mysql> create table firsttable(
-> id varchar(64), 
-> name varchar(64), 
-> flag char(1), 
-> primary key (id), 
-> key key_name (name), 
-> key key_flag (flag) 
-> );

挿入データ：

mysql> insert into firsttable values(uuid(), 'test', '0'); 
Query OK, 1 row affected (0.10 sec) 
mysql> insert into firsttable values(uuid(), 'test1', '0'); 
Query OK, 1 row affected (0.10 sec)

問い合わせ：

mysql> select * from firsttable where name ='test'; 
+--------------------------------------+------+------+ 
| id         | name | flag | 
+--------------------------------------+------+------+ 
| d72bfd53-8fd6-11e7-baee-54ee7597a644 | test | 0 | 
+--------------------------------------+------+------+ 
1 row in set (0.00 sec) 

mysql> select * from firsttable where name ='test' and flag='0'; 
ERROR 2013 (HY000): Lost connection to MySQL server during query 
mysql>

エラーログ：

2017-09-03T05:07:46.275435Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 
 
2017-09-03T05:07:46.275435Z 0 [Note] --secure-file-priv is set to NULL. Operations related to importing and exporting data are disabled 
 
2017-09-03T05:07:46.275435Z 0 [Note] MySQL (mysqld 5.7.19) starting as process 8964 ... 
 
2017-09-03T05:07:46.283435Z 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 
 
2017-09-03T05:07:46.284435Z 0 [Note] InnoDB: Uses event mutexes 
 
2017-09-03T05:07:46.285436Z 0 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier 
 
2017-09-03T05:07:46.285436Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.3 
 
2017-09-03T05:07:46.286436Z 0 [Note] InnoDB: Number of pools: 1 
 
2017-09-03T05:07:46.287436Z 0 [Note] InnoDB: Not using CPU crc32 instructions 
 
2017-09-03T05:07:46.290436Z 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M 
 
2017-09-03T05:07:46.298436Z 0 [Note] InnoDB: Completed initialization of buffer pool 
 
2017-09-03T05:07:46.448445Z 0 [Note] InnoDB: Highest supported file format is Barracuda. 
 
2017-09-03T05:07:46.472446Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 2568065 
 
2017-09-03T05:07:46.473446Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 2568074 
 
2017-09-03T05:07:46.475446Z 0 [Note] InnoDB: Database was not shutdown normally! 
 
2017-09-03T05:07:46.476446Z 0 [Note] InnoDB: Starting crash recovery. 
 
2017-09-03T05:07:46.758463Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 
 
2017-09-03T05:07:46.760463Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables 
 
2017-09-03T05:07:46.761463Z 0 [Note] InnoDB: Setting file '.\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 
 
2017-09-03T05:07:46.939473Z 0 [Note] InnoDB: File '.\ibtmp1' size is now 12 MB. 
 
2017-09-03T05:07:46.946473Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active. 
 
2017-09-03T05:07:46.950474Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active. 
 
2017-09-03T05:07:46.954474Z 0 [Note] InnoDB: Waiting for purge to start 
 
2017-09-03T05:07:47.012477Z 0 [Note] InnoDB: 5.7.19 started; log sequence number 2568074 
 
2017-09-03T05:07:47.014477Z 0 [Note] InnoDB: Loading buffer pool(s) from D:\Program Files\mysql-5.7.19-winx64\data\ib_buffer_pool 
 
2017-09-03T05:07:47.014477Z 0 [Note] Plugin 'FEDERATED' is disabled. 
 
2017-09-03T05:07:47.049479Z 0 [Warning] Failed to set up SSL because of the following SSL library error: SSL context is not usable without certificate and private key 
 
2017-09-03T05:07:47.052479Z 0 [Note] Server hostname (bind-address): '*'; port: 3306 
 
2017-09-03T05:07:47.057480Z 0 [Note] IPv6 is available. 
 
2017-09-03T05:07:47.058480Z 0 [Note] - '::' resolves to '::'; 
 
2017-09-03T05:07:47.059480Z 0 [Note] Server socket created on IP: '::'. 
 
2017-09-03T05:07:47.322495Z 0 [Note] Event Scheduler: Loaded 0 events 
 
2017-09-03T05:07:47.323495Z 0 [Note] MySQL: ready for connections. 
 
Version: '5.7.19' socket: '' port: 3306 MySQL Community Server (GPL) 
 
2017-09-03T05:07:47.325495Z 0 [Note] Executing 'SELECT * FROM INFORMATION_SCHEMA.TABLES;' to get a list of tables using the deprecated partition engine. You may use the startup option '--disable-partition-engine-check' to skip this check. 
 
2017-09-03T05:07:47.327495Z 0 [Note] Beginning of list of non-natively partitioned tables 
 
2017-09-03T05:07:47.356497Z 0 [Note] End of list of non-natively partitioned tables 
 
2017-09-03T05:07:47.365497Z 0 [Note] InnoDB: Buffer pool(s) load completed at 170903 13:07:47 
 
05:08:53 UTC - mysqld got exception 0xc000001d ; 
 
This could be because you hit a bug. It is also possible that this binary 
 
or one of the libraries it was linked against is corrupt, improperly built, 
 
or misconfigured. This error can also be caused by malfunctioning hardware. 
 
Attempting to collect some information that could help diagnose the problem. 
 
As this is a crash and something is definitely wrong, the information 
 
collection process might fail. 
 

 
key_buffer_size=8388608 
 
read_buffer_size=131072 
 
max_used_connections=1 
 
max_threads=200 
 
thread_count=1 
 
connection_count=1 
 
It is possible that mysqld could use up to 
 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 87423 K bytes of memory 
 
Hope that's ok; if not, decrease some variables in the equation. 
 

 
Thread pointer: 0x135e5400 
 
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... 
 
7fef78e5c01 MSVCR120.dll!pow() 
 
13f5e5f7a mysqld.exe!get_sweep_read_cost()[handler.cc:7199] 
 
13fba7b37 mysqld.exe!ror_intersect_add()[opt_range.cc:5461] 
 
13fb9da89 mysqld.exe!get_best_ror_intersect()[opt_range.cc:5642] 
 
13fba9e25 mysqld.exe!test_quick_select()[opt_range.cc:3108] 
 
13f756a3e mysqld.exe!get_quick_record_count()[sql_optimizer.cc:5948] 
 
13f75549d mysqld.exe!JOIN::estimate_rowcount()[sql_optimizer.cc:5694] 
 
13f758209 mysqld.exe!JOIN::make_join_plan()[sql_optimizer.cc:5051] 
 
13f759d7b mysqld.exe!JOIN::optimize()[sql_optimizer.cc:368] 
 
13f7a2149 mysqld.exe!st_select_lex::optimize()[sql_select.cc:1009] 
 
13f7a016d mysqld.exe!handle_query()[sql_select.cc:164] 
 
13f613f17 mysqld.exe!execute_sqlcom_select()[sql_parse.cc:5158] 
 
13f615e46 mysqld.exe!mysql_execute_command()[sql_parse.cc:2795] 
 
13f6198a3 mysqld.exe!mysql_parse()[sql_parse.cc:5580] 
 
13f612953 mysqld.exe!dispatch_command()[sql_parse.cc:1464] 
 
13f61398a mysqld.exe!do_command()[sql_parse.cc:1001] 
 
13f5ba4dc mysqld.exe!handle_connection()[connection_handler_per_thread.cc:300] 
 
1400143a2 mysqld.exe!pfs_spawn_thread()[pfs.cc:2191] 
 
13fd2743c mysqld.exe!win_thread_start()[my_thread.c:38] 
 
7fef7874f7f MSVCR120.dll!_beginthreadex() 
 
7fef7875126 MSVCR120.dll!_endthreadex() 
 
7729f56d kernel32.dll!BaseThreadInitThunk() 
 
774d3281 ntdll.dll!RtlUserThreadStart() 
 

 
Trying to get some variables. 
 
Some pointers may be invalid and cause the dump to abort. 
 
Query (135700a0): select * from firsttable where name ='test' and flag='0' 
 
Connection ID (thread ID): 3 
 
Status: NOT_KILLED 
 

 
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains 
 
information that should help you find out what is causing the crash.

出典

2017-09-02 Wenbo Ding

重複https://stackoverflow.com/questions/41476778/mysql-crash-when-querying？ – BitAccesser

私は問題を見て、彼は10の問題を解決するために更新プログラムを言ったが、私はまだあなたの編集のために7を使用して勝利を使用したい。 –

いいえ、彼はService Pack 1へのアップデートが問題を解決したと言いました。 Win7 SP1に更新する必要があります。 – BitAccesser

が、私はエラーを再現しようと、私はエラーを取得していない、私はそれを置くましょう：

mysql> create table firsttable 
    -> (
    -> id varchar(64), 
    -> name varchar(64), 
    -> flag char(1), 
    -> primary key(id), 
    -> key key_name (name), 
    -> key key_flag (flag) 
    ->); 
Query OK, 0 rows affected (1.12 sec) 

mysql> insert into firsttable values(uuid(), 'test', '0'); 
Query OK, 1 row affected (0.20 sec) 

mysql> insert into firsttable values(uuid(), 'test1', '0'); 
Query OK, 1 row affected (0.08 sec) 

mysql> select * from firsttable where name ='test'; 
+--------------------------------------+------+------+ 
| id         | name | flag | 
+--------------------------------------+------+------+ 
| 7c89e986-9000-11e7-a1f8-507b9dc06264 | test | 0 | 
+--------------------------------------+------+------+ 
1 row in set (0.09 sec) 

mysql> select * from firsttable where name ='test' and flag='0'; 
+--------------------------------------+------+------+ 
| id         | name | flag | 
+--------------------------------------+------+------+ 
| 7c89e986-9000-11e7-a1f8-507b9dc06264 | test | 0 | 
+--------------------------------------+------+------+ 
1 row in set (0.09 sec) 

mysql>

私は結論付けることができ、MySQL crashは、このSQL文によるものではありません。エラーログからは、MSVCR120.dllにいくつかの問題があるようです。さらに分析するには、完全なエラーログを共有してください。通常、破損した文はKILL signalの前にキャプチャされます。これがあなたに役立つことを願っています。ありがとう！

出典

2017-09-02 17:16:18 rathishDBA

質問を編集し、完全なエラーログを投稿しました。ありがとう。 –

Win7 SP1へのアップデートにより、この問題は解決しました。 BitAccesserの助けを借りて、私は他の似たような質問を慎重に見ていません。 –

x64のVC再配布可能ファイルを再インストールしてください。 Download vcredist_x64.exe

出典

2017-09-02 17:19:46

vc redistributablesをx64（2010、2013）に再インストールしましたが、動作しません。 –

Win7 SP1へのアップデートにより、この問題が解決します。 BitAccesserの助けを借りて、私は他の似たような質問を慎重に見ていません。 –

複数の条件でクエリを実行すると、mysqlがクラッシュする

答えて

関連する問題