首页 / MYSQL / Mysql查看sql是否走事务
Mysql查看sql是否走事务
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了Mysql查看sql是否走事务,小编现在分享给大家,供广大互联网技能从业者学习和参考。文章包含6667字,纯文字阅读大概需要10分钟。
内容图文
![Mysql查看sql是否走事务](/upload/InfoBanner/zyjiaocheng/484/862c784023c04e0c83b92a5e5139deea.jpg)
[root@gzmtest_25 ~]# su - mysql [mysql@gzmtest_25 ~]$ mysql.local Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 126000553 Server version: 5.5.27-log Sourcedistribution Copyright (c) 2000, 2011, Oracle and/or itsaffiliates. All rights reserved. Oracle is a registered trademark of OracleCorporation and/or its affiliates. Other names may be trademarksof their respective owners. Type ‘help;‘ or ‘\h‘ for help. Type ‘\c‘ toclear the current input statement.
能够看到监控日志是否开启的选项(off是关闭)on是开启
root@localhost:(none)>show global variables like ‘general_log%‘; +------------------+---------------------------+ | Variable_name | Value | +------------------+---------------------------+ | general_log | OFF | | general_log_file |/data/mysql/log/mysql.log | +------------------+---------------------------+ 2 rows in set (0.01 sec) root@localhost:(none)> root@localhost:(none)>set global general_log=on; Query OK, 0 rows affected (0.02 sec)
查看当前系统日志大小
root@localhost:(none)>system du -h /data/mysql/log/mysql.log 1.7M /data/mysql/log/mysql.log
开启日志成功
接下来就能够直接进入shell中依据sql特征来查看我们sql会话信息
[root@gzmtest_25 ~]# grep "forupdate" /data/mysql/log/mysql.log 126002192 Query select pk fromT_GANTT_CHART where pk =47 for update <p>//忽略其它的数据了。</p>
运行看当前会话的信息
[root@gzmtest_25~]# grep 126002192 /data/mysql/log/mysql.log 126002192Connect test@11.104.32.115 on test 126002192Query /* mysql-connector-java-5.1.6 (Revision: ${svn.Revision} ) */SHOW VARIABLES WHERE Variable_name =‘language‘ ORVariable_name = ‘net_write_timeout‘ OR Variable_name = ‘interactive_timeout‘ ORVariable_name = ‘wait_timeout‘ OR Variable_name = ‘character_set_client‘ ORVariable_name = ‘character_set_connection‘ OR Variable_name = ‘character_set‘OR Variable_name = ‘character_set_server‘ OR Variable_name = ‘tx_isolation‘ ORVariable_name = ‘transaction_isolation‘ OR Variable_name =‘character_set_results‘ OR Variable_name = ‘timezone‘ OR Variable_name =‘time_zone‘ OR Variable_name = ‘system_time_zone‘ OR Variable_name =‘lower_case_table_names‘ OR Variable_name = ‘max_allowed_packet‘ ORVariable_name = ‘net_buffer_length‘ OR Variable_name = ‘sql_mode‘ ORVariable_name = ‘query_cache_type‘ OR Variable_name = ‘query_cache_size‘ ORVariable_name = ‘init_connect‘ 126002192Query SHOW COLLATION 126002192Query SET character_set_results = NULL 126002192Query SET autocommit=1 126002192Query SETsql_mode=‘STRICT_TRANS_TABLES‘ 141017 11:20:49 126002192 Query SETautocommit=0 126002192Query commit 126002192Query SET autocommit=1 126002192Query select *....sql 太长忽略 126002192Query SELECTCOUNT(last_password_change) FROM T_PF_USER 126002192Query SELECT COUNT(password_salt) FROMT_PF_USER 126002192Query SELECT COUNT(comment_of_attendee)FROM T_PLUGIN_CALENDAR_EVENT_ATTENDEE 126002192Query SELECT COUNT(ext_subscription)FROM T_PLUGIN_CALENDAR 126002192Query SELECTCOUNT(ext_subscription_calendar_binary) FROM T_PLUGIN_CALENDAR 126002192Query SELECTCOUNT(ext_subscription_hash) FROM T_PLUGIN_CALENDAR 126002192Query SELECTCOUNT(ext_subscription_url) FROM T_PLUGIN_CALENDAR 126002192Query SELECTCOUNT(ext_subscription_update_interval) FROM T_PLUGIN_CALENDAR 126002192Query SELECT COUNT(*) FROMT_PLUGIN_TODO 126002192Query SELECT COUNT(*) FROMT_PLUGIN_MEMO //sql太长忽略 126002192Query SELECT @@session.tx_isolation 126002192Query SET SESSION TRANSACTION ISOLATIONLEVEL REPEATABLE READ 126002192Query SET autocommit=0 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select pk from T_GANTT_CHARTwhere pk =47 for update 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query select *....sql 太长忽略 126002192Query update T_GANTT_OBJECT setcreated=‘2014-08-19 16:56:49‘, deleted=0, last_update=‘2014-08-23 14:20:42‘,duration=0, endDate=‘2014-08-13 00:00:00‘, oId=-1, orderValue=20, parentId=237,preId=-1, predecessorOffset=0, progress=100, refId=-1, relationType=‘start_start‘,startDate=‘2014-08-05 00:00:00‘, id=96, title=‘01_系统设计‘,type=‘activity‘, visible=1 where pk=238 126002192Query update T_GANTT_CHART setcreated=‘2014-08-19 16:56:49‘, deleted=0, last_update=‘2014-10-17 11:22:18‘,gantt_objects_as_xml=237, name=‘3D项目‘, owner_fk=8,read_access=‘ALL‘, settings_as_xml=‘<ganttChartSettings><title>3D项目</title><openNodes/></ganttChartSettings>‘,style_as_xml=‘<ganttChartStyle xTicks="AUTO"width="1000"/>‘, task_fk=94, write_access=‘ALL‘ where pk=47 126002192Query update T_GANTT_OBJECT setcreated=‘2014-08-19 17:57:01‘, deleted=0, last_update=‘2014-08-23 14:20:42‘,duration=0, endDate=‘2014-10-18 00:00:00‘, oId=3, orderValue=20, parentId=241,preId=219, predecessorOffset=0, progress=null, refId=2, relationType=‘start_start‘,startDate=‘2014-10-15 00:00:00‘, id=100, title=‘促销数据‘,type=‘activity‘, visible=1 where pk=243 126002192Query commit 126002192Query SET autocommit=1 126002192Query SET SESSION TRANSACTION ISOLATIONLEVEL READ COMMITTED
依据上面的日志明显能够断定了:
当设置SET autocommit=1 之后的sql都是没有走事务的,
当SET autocommit=0之后到commit之前的都是走了事务的。
记要完成。
分析完成后别忘记把日志关闭,不然非常影响性能的哦
root@localhost:(none)>set global general_log=off; Query OK, 0 rows affected (0.00 sec) root@localhost:(none)>show global variables like ‘general_log%‘; +------------------+---------------------------+ | Variable_name | Value | +------------------+---------------------------+ | general_log | OFF | | general_log_file |/data/mysql/log/mysql.log | +------------------+---------------------------+ 2 rows in set (0.00 sec) root@localhost:(none)>
Mysql查看sql是否走事务
标签:1.7 from read 设计 mod root copyright track 忘记
本文系统来源:http://www.cnblogs.com/lytwajue/p/6939776.html
内容总结
以上是互联网集市为您收集整理的Mysql查看sql是否走事务全部内容,希望文章能够帮你解决Mysql查看sql是否走事务所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错,欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 gblab@vip.qq.com 举报,一经查实,本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。