데이터 베이스 MySQL 튜토리얼 [mysqldumpslow 出错] Died at /usr/local/mysql/bin/mysqldumps

[mysqldumpslow 出错] Died at /usr/local/mysql/bin/mysqldumps

Jun 07, 2016 pm 04:25 PM
usr 오류

[mysqldumpslow 报错] Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236. mysqldumpslow报错: Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236. 总结:是因为top数目太多了,mysqldumpslow遍历不过来的缘故。 /usr/local/m

[mysqldumpslow 报错] Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236.

mysqldumpslow报错:Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236.

总结:是因为top数目太多了,mysqldumpslow遍历不过来的缘故。

/usr/local/mysql/bin/mysqldumpslow -s -t 15 /root/db01-102-slow.log 


1,把r去掉试试,还是报错,参数不识别。

[root@slave ]# /usr/local/mysql/bin/mysqldumpslow -s -t 15 /root/db01-102-slow.log 

Reading mysql slow query log from 15 /root/db01-102-slow.log
Can't open 15: 没有那个文件或目录 at /usr/local/mysql/bin/mysqldumpslow line 91.
Count: 22  Time=9.61s (211s)  Lock=0.00s (0s)  Rows=1.0 (22), [dubbo]@2hosts
  select count(*)
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id

Count: 177  Time=1.40s (247s)  Lock=0.00s (0s)  Rows=1.0 (177), [dubbo]@2hosts
  select count(*) from user_info
  LEFT JOIN system_region a
  ON province_id =a.region_id
  LEFT JOIN system_region b
  ON city_id = b.region_id
  LEFT JOIN system_region c
  ON district_id = c.region_id

Count: 22  Time=13.20s (290s)  Lock=0.00s (0s)  Rows=10.0 (220), [dubbo]@2hosts
  select 
  coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark,
  coupon.code,  coupon_lot.coupon_type, coupon.state,
  coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, 
  coupon_lot.is_reusable, coupon_lot.start_datetime,
  coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department,
  coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category,
  coupon_lot.pdt_code,brand.brand_name,product_category.category_name
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id
  group by coupon_lot.coupon_lot_id
  order by coupon_lot.create_datetime DESC
  limit N,N

Count: 8  Time=1.09s (8s)  Lock=0.00s (0s)  Rows=10.0 (80), [dubbo]@2hosts
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  limit N,N

Count: 1  Time=1.00s (1s)  Lock=0.00s (0s)  Rows=1.0 (1), root[root]@localhost
  select sleep(N)

Count: 1  Time=1.13s (1s)  Lock=0.00s (0s)  Rows=10.0 (10), [dubbo]@[xx]
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  , oi.order_sn 
  limit N,N

Count: 5  Time=2.47s (12s)  Lock=0.00s (0s)  Rows=0.0 (0), [dubbo]@2hosts
  select
  user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, 
  birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, 
  active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, 
  tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, 
  verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, 
  verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel
  from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S')
로그인 후 복사

2,查看下mysqldumpslow 使用参数,-s后面需要带参数的,看了西夏at比较合适

[root@db-master-2 ~]# /usr/local/mysql/bin/mysqldumpslow  --help
Usage: mysqldumpslow [ OPTS... ] [ LOGS... ]

Parse and summarize the MySQL slow query log. Options are

  --verbose    verbose
  --debug      debug
  --help       write this text to standard output

  -v           verbose
  -d           debug
  -s ORDER     what to sort by (al, at, ar, c, l, r, t), 'at' is default
                al: average lock time
                ar: average rows sent
                at: average query time
                 c: count
                 l: lock time
                 r: rows sent
                 t: query time  
  -r           reverse the sort order (largest last instead of first)
  -t NUM       just show the top n queries
  -a           don't abstract all numbers to N and strings to 'S'
  -n NUM       abstract numbers with at least n digits within names
  -g PATTERN   grep: only consider stmts that include this string
  -h HOSTNAME  hostname of db server for *-slow.log filename (can be wildcard),
               default is '*', i.e. match all
  -i NAME      name of server instance (if using mysql.server startup script)
  -l           don't subtract lock time from total time
로그인 후 복사


3,在mysqldumpslow的-s后面加入 at参数试试:  [root@slave ]# /usr/local/mysql/bin/mysqldumpslow -s at -t 15 /root/db01-102-slow.log 

[root@db-master-2 ~]# /usr/local/mysql/bin/mysqldumpslow -s at -t 15 /root/db01-102-slow.log 
Reading mysql slow query log from /root/db01-102-slow.log
Count: 22  Time=13.20s (290s)  Lock=0.00s (0s)  Rows=10.0 (220), [dubbo]@2hosts
  select 
  coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark,
  coupon.code,  coupon_lot.coupon_type, coupon.state,
  coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, 
  coupon_lot.is_reusable, coupon_lot.start_datetime,
  coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department,
  coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category,
  coupon_lot.pdt_code,brand.brand_name,product_category.category_name
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id
  group by coupon_lot.coupon_lot_id
  order by coupon_lot.create_datetime DESC
  limit N,N

Count: 22  Time=9.61s (211s)  Lock=0.00s (0s)  Rows=1.0 (22), [dubbo]@2hosts
  select count(*)
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id

Count: 5  Time=2.47s (12s)  Lock=0.00s (0s)  Rows=0.0 (0), [dubbo]@2hosts
  select
  user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, 
  birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, 
  active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, 
  tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, 
  verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, 
  verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel
  from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S')

Count: 177  Time=1.40s (247s)  Lock=0.00s (0s)  Rows=1.0 (177), [dubbo]@2hosts
  select count(*) from user_info
  LEFT JOIN system_region a
  ON province_id =a.region_id
  LEFT JOIN system_region b
  ON city_id = b.region_id
  LEFT JOIN system_region c
  ON district_id = c.region_id

Count: 1  Time=1.13s (1s)  Lock=0.00s (0s)  Rows=10.0 (10), [dubbo]@[10.10.3.8]
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  , oi.order_sn 
  limit N,N

Count: 8  Time=1.09s (8s)  Lock=0.00s (0s)  Rows=10.0 (80), [dubbo]@2hosts
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  limit N,N

Count: 1  Time=1.00s (1s)  Lock=0.00s (0s)  Rows=1.0 (1), root[root]@localhost
  select sleep(N)

Died at /usr/local/mysql/bin/mysqldumpslow line 161,  chunk 236.
로그인 후 복사
看到后面还是报错:Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236.

4,去看看/usr/local/mysql/bin/mysqldumpslow的第161行左右,到底是在操作什么脚本。

156 my @sorted = sort { $stmt{$b}->{$opt{s}}  $stmt{$a}->{$opt{s}} } keys %stmt;
157 @sorted = @sorted[0 .. $opt{t}-1] if $opt{t};
158 @sorted = reverse @sorted         if $opt{r};
159 
160 foreach (@sorted) {
161     my $v = $stmt{$_} || die;
162     my ($c, $t,$at, $l,$al, $r,$ar) = @{ $v }{qw(c t at l al r ar)};
163     my @users = keys %{$v->{users}};
164     my $user  = (@users==1) ? $users[0] : sprintf "%dusers",scalar @users;
165     my @hosts = keys %{$v->{hosts}};
166     my $host  = (@hosts==1) ? $hosts[0] : sprintf "%dhosts",scalar @hosts;
167     printf "Count: %d  Time=%.2fs (%ds)  Lock=%.2fs (%ds)  Rows=%.1f (%d), $user\@$host\n%s\n\n",
168             $c, $at,$t, $al,$l, $ar,$r, $_;
169 }
170 
171 sub usage {
172     my $str= shift;
로그인 후 복사
看到主要是foreach (@sorted)遍历函数,也就是遍历到chunk 236的时候就died结束了,没有办法往下继续foreach了。因为以前写过代码,知道报错所在的这一行

 my $v = $stmt{$_} || die;
로그인 후 복사
是遍历第一句,那么肯定是赋值语句,报错Died,chunk 236肯定是已经遍历到末尾没有数据了,看这个函数没有判断传入的参数是否为null的逻辑,所以当文件数据已经遍历完,但是命令还没有结束,所以继续遍历,遍历null的时候报错,所以进程中止了,解决办法就是做个限制不要遍历超过原始数据的字符串长度。那么我们再来看执行的命令:

 /usr/local/mysql/bin/mysqldumpslow -s at -t 15 /root/db01-102-slow.log 有 -t 15这一句,那么就是要显示出前15个记录,那么如果我的slow.log统计出来只有12个不到15个,而这里有继续遍历到15的话,那进程肯定会Died。


所以这里有2个解决方法:

1 修改/usr/local/mysql/bin/mysqldumpslow里面的源代码,加null判断。

这个过程有些复杂,暂时略过吧,期待后续空了再研究。


2 修改命令  /usr/local/mysql/bin/mysqldumpslow -s at -t 15 /root/db01-102-slow.log ,把-t 15修改成-t 10或者-t 5试试。

试了好几次,发现临界点在-t 7上面,如下:

[root@slave~]# /usr/local/mysql/bin/mysqldumpslow -s at -t 8 /root/db01-102-slow.log 
Reading mysql slow query log from /root/db01-102-slow.log
Count: 22  Time=13.20s (290s)  Lock=0.00s (0s)  Rows=10.0 (220), [dubbo]@2hosts
  select 
  coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark,
  coupon.code,  coupon_lot.coupon_type, coupon.state,
  coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, 
  coupon_lot.is_reusable, coupon_lot.start_datetime,
  coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department,
  coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category,
  coupon_lot.pdt_code,brand.brand_name,product_category.category_name
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id
  group by coupon_lot.coupon_lot_id
  order by coupon_lot.create_datetime DESC
  limit N,N

Count: 22  Time=9.61s (211s)  Lock=0.00s (0s)  Rows=1.0 (22), [dubbo]@2hosts
  select count(*)
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id

Count: 5  Time=2.47s (12s)  Lock=0.00s (0s)  Rows=0.0 (0), [dubbo]@2hosts
  select
  user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, 
  birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, 
  active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, 
  tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, 
  verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, 
  verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel
  from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S')

Count: 177  Time=1.40s (247s)  Lock=0.00s (0s)  Rows=1.0 (177), [xx]@2hosts
  select count(*) from user_info
  LEFT JOIN system_region a
  ON province_id =a.region_id
  LEFT JOIN system_region b
  ON city_id = b.region_id
  LEFT JOIN system_region c
  ON district_id = c.region_id

Count: 1  Time=1.13s (1s)  Lock=0.00s (0s)  Rows=10.0 (10), [xx]@[xxx]
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  , oi.order_sn 
  limit N,N

Count: 8  Time=1.09s (8s)  Lock=0.00s (0s)  Rows=10.0 (80), [xx]@2hosts
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  limit N,N

Count: 1  Time=1.00s (1s)  Lock=0.00s (0s)  Rows=1.0 (1), root[root]@localhost
  select sleep(N)

Died at /usr/local/mysql/bin/mysqldumpslow line 161,  chunk 236.

-- 临界点 -t 7
[root@db-master-2 ~]# /usr/local/mysql/bin/mysqldumpslow -s at -t 7 /root/db01-102-slow.log 

Reading mysql slow query log from /root/db01-102-slow.log
Count: 22  Time=13.20s (290s)  Lock=0.00s (0s)  Rows=10.0 (220), [xx]@2hosts
  select 
  coupon_id, coupon_lot.coupon_lot_id, coupon_lot.remark,
  coupon.code,  coupon_lot.coupon_type, coupon.state,
  coupon_lot.ckey, coupon_lot.cvalue, coupon_lot.discount, coupon_lot.type, coupon_lot.channel, 
  coupon_lot.is_reusable, coupon_lot.start_datetime,
  coupon_lot.end_datetime, coupon_lot.create_datetime, coupon.update_datetime ,coupon_lot.department,
  coupon_lot.state as couponLotState, coupon_lot.create_operator,coupon_lot.coupon_category,
  coupon_lot.pdt_code,brand.brand_name,product_category.category_name
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id
  group by coupon_lot.coupon_lot_id
  order by coupon_lot.create_datetime DESC
  limit N,N

Count: 22  Time=9.61s (211s)  Lock=0.00s (0s)  Rows=1.0 (22), [dubbo]@2hosts
  select count(*)
  from coupon_lot
  left join coupon 
  on coupon.coupon_lot_id = coupon_lot.coupon_lot_id
  LEFT JOIN brand
  ON brand.brand_id=coupon_lot.brand_id
  LEFT JOIN product_category
  on product_category.category_id=coupon_lot.category_id

Count: 5  Time=2.47s (12s)  Lock=0.00s (0s)  Rows=0.0 (0), [xx]@2hosts
  select
  user_id, usename, nickname, password, user_group_id, realname, gender, email, mobilephone, 
  birthday, province_id, city_id, district_id, marry, income, remarks, create_datetime, 
  active_state, verityEmail, verityPhone, credit, last_login, last_ip, is_locked, channel, 
  tag, union_partner_uuid, union_user_safekey, is_black, qq, weibo_id, verity_email_key, 
  verity_phone_key, verity_email_datetime, verity_phone_datetime, verity_question, 
  verity_answer, cps_code, cps_time_from, cps_time_to, cps_cookie, first_channel
  from user_info where mobilephone = 'S' and (channel is null or trim(channel) ='S')

Count: 177  Time=1.40s (247s)  Lock=0.00s (0s)  Rows=1.0 (177), [xx]@2hosts
  select count(*) from user_info
  LEFT JOIN system_region a
  ON province_id =a.region_id
  LEFT JOIN system_region b
  ON city_id = b.region_id
  LEFT JOIN system_region c
  ON district_id = c.region_id

Count: 1  Time=1.13s (1s)  Lock=0.00s (0s)  Rows=10.0 (10), [dubbo]@[xxx]
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  , oi.order_sn 
  limit N,N

Count: 8  Time=1.09s (8s)  Lock=0.00s (0s)  Rows=10.0 (80), [dubbo]@2hosts
  select 
  return_sn,  relating_order_sn, return_from,  oi.order_out_sn ,
  add_time , return_type, 
  return_pay, ui.usename as userName, return_consignee, return_goods_count ,
  return_total_fee, total_paid, 
  return_desc, return_order_status,  return_pay_status ,
  return_shipping_status, order_return.lock_operator, order_return.return_invoice_no
  from order_return  LEFT JOIN   order_info oi
  on order_return.relating_order_sn = oi.order_sn 
  left join user_info ui on oi.user_id = ui.user_id
  left join order_payment on order_payment.order_sn = oi.order_sn
  order by order_return.add_time DESC
  limit N,N

Count: 1  Time=1.00s (1s)  Lock=0.00s (0s)  Rows=1.0 (1), root[root]@localhost
  select sleep(N)

[root@db-master-2 ~]# 
로그인 후 복사

最终总结:
mysqldumpslow报错:Died at /usr/local/mysql/bin/mysqldumpslow line 161, chunk 236. 是因为top数目太多了,mysqldumpslow遍历不过来的缘故。

본 웹사이트의 성명
본 글의 내용은 네티즌들의 자발적인 기여로 작성되었으며, 저작권은 원저작자에게 있습니다. 본 사이트는 이에 상응하는 법적 책임을 지지 않습니다. 표절이나 침해가 의심되는 콘텐츠를 발견한 경우 admin@php.cn으로 문의하세요.

핫 AI 도구

Undresser.AI Undress

Undresser.AI Undress

사실적인 누드 사진을 만들기 위한 AI 기반 앱

AI Clothes Remover

AI Clothes Remover

사진에서 옷을 제거하는 온라인 AI 도구입니다.

Undress AI Tool

Undress AI Tool

무료로 이미지를 벗다

Clothoff.io

Clothoff.io

AI 옷 제거제

AI Hentai Generator

AI Hentai Generator

AI Hentai를 무료로 생성하십시오.

인기 기사

R.E.P.O. 에너지 결정과 그들이하는 일 (노란색 크리스탈)
1 몇 달 전 By 尊渡假赌尊渡假赌尊渡假赌
R.E.P.O. 최고의 그래픽 설정
1 몇 달 전 By 尊渡假赌尊渡假赌尊渡假赌
Will R.E.P.O. 크로스 플레이가 있습니까?
1 몇 달 전 By 尊渡假赌尊渡假赌尊渡假赌

뜨거운 도구

메모장++7.3.1

메모장++7.3.1

사용하기 쉬운 무료 코드 편집기

SublimeText3 중국어 버전

SublimeText3 중국어 버전

중국어 버전, 사용하기 매우 쉽습니다.

스튜디오 13.0.1 보내기

스튜디오 13.0.1 보내기

강력한 PHP 통합 개발 환경

드림위버 CS6

드림위버 CS6

시각적 웹 개발 도구

SublimeText3 Mac 버전

SublimeText3 Mac 버전

신 수준의 코드 편집 소프트웨어(SublimeText3)

InnoDB 전체 텍스트 검색 기능을 설명하십시오. InnoDB 전체 텍스트 검색 기능을 설명하십시오. Apr 02, 2025 pm 06:09 PM

InnoDB의 전체 텍스트 검색 기능은 매우 강력하여 데이터베이스 쿼리 효율성과 대량의 텍스트 데이터를 처리 할 수있는 능력을 크게 향상시킬 수 있습니다. 1) InnoDB는 기본 및 고급 검색 쿼리를 지원하는 역 색인화를 통해 전체 텍스트 검색을 구현합니다. 2) 매치 및 키워드를 사용하여 검색, 부울 모드 및 문구 검색을 지원합니다. 3) 최적화 방법에는 워드 세분화 기술 사용, 인덱스의 주기적 재건 및 캐시 크기 조정, 성능과 정확도를 향상시키는 것이 포함됩니다.

Alter Table 문을 사용하여 MySQL에서 테이블을 어떻게 변경합니까? Alter Table 문을 사용하여 MySQL에서 테이블을 어떻게 변경합니까? Mar 19, 2025 pm 03:51 PM

이 기사는 MySQL의 Alter Table 문을 사용하여 열 추가/드롭 테이블/열 변경 및 열 데이터 유형 변경을 포함하여 테이블을 수정하는 것에 대해 설명합니다.

MySQL에서 인덱스를 사용하는 것보다 전체 테이블 스캔이 더 빠를 수 있습니까? MySQL에서 인덱스를 사용하는 것보다 전체 테이블 스캔이 더 빠를 수 있습니까? Apr 09, 2025 am 12:05 AM

전체 테이블 스캔은 MySQL에서 인덱스를 사용하는 것보다 빠를 수 있습니다. 특정 사례는 다음과 같습니다. 1) 데이터 볼륨은 작습니다. 2) 쿼리가 많은 양의 데이터를 반환 할 때; 3) 인덱스 열이 매우 선택적이지 않은 경우; 4) 복잡한 쿼리시. 쿼리 계획을 분석하고 인덱스 최적화, 과도한 인덱스를 피하고 정기적으로 테이블을 유지 관리하면 실제 응용 프로그램에서 최상의 선택을 할 수 있습니다.

Windows 7에 MySQL을 설치할 수 있습니까? Windows 7에 MySQL을 설치할 수 있습니까? Apr 08, 2025 pm 03:21 PM

예, MySQL은 Windows 7에 설치 될 수 있으며 Microsoft는 Windows 7 지원을 중단했지만 MySQL은 여전히 ​​호환됩니다. 그러나 설치 프로세스 중에 다음 지점이 표시되어야합니다. Windows 용 MySQL 설치 프로그램을 다운로드하십시오. MySQL의 적절한 버전 (커뮤니티 또는 기업)을 선택하십시오. 설치 프로세스 중에 적절한 설치 디렉토리 및 문자를 선택하십시오. 루트 사용자 비밀번호를 설정하고 올바르게 유지하십시오. 테스트를 위해 데이터베이스에 연결하십시오. Windows 7의 호환성 및 보안 문제에 주목하고 지원되는 운영 체제로 업그레이드하는 것이 좋습니다.

MySQL 연결에 대한 SSL/TLS 암호화를 어떻게 구성합니까? MySQL 연결에 대한 SSL/TLS 암호화를 어떻게 구성합니까? Mar 18, 2025 pm 12:01 PM

기사는 인증서 생성 및 확인을 포함하여 MySQL에 대한 SSL/TLS 암호화 구성에 대해 설명합니다. 주요 문제는 자체 서명 인증서의 보안 영향을 사용하는 것입니다. [문자 수 : 159]

인기있는 MySQL GUI 도구는 무엇입니까 (예 : MySQL Workbench, Phpmyadmin)? 인기있는 MySQL GUI 도구는 무엇입니까 (예 : MySQL Workbench, Phpmyadmin)? Mar 21, 2025 pm 06:28 PM

기사는 MySQL Workbench 및 Phpmyadmin과 같은 인기있는 MySQL GUI 도구에 대해 논의하여 초보자 및 고급 사용자를위한 기능과 적합성을 비교합니다. [159 자].

InnoDB에서 클러스터 된 인덱스와 비 클러스터 된 인덱스 (2 차 지수)의 차이. InnoDB에서 클러스터 된 인덱스와 비 클러스터 된 인덱스 (2 차 지수)의 차이. Apr 02, 2025 pm 06:25 PM

클러스터 인덱스와 비 클러스터 인덱스의 차이점은 1. 클러스터 된 인덱스는 인덱스 구조에 데이터 행을 저장하며, 이는 기본 키 및 범위별로 쿼리에 적합합니다. 2. 클러스터되지 않은 인덱스는 인덱스 키 값과 포인터를 데이터 행으로 저장하며 비 예산 키 열 쿼리에 적합합니다.

MySQL에서 큰 데이터 세트를 어떻게 처리합니까? MySQL에서 큰 데이터 세트를 어떻게 처리합니까? Mar 21, 2025 pm 12:15 PM

기사는 MySQL에서 파티셔닝, 샤딩, 인덱싱 및 쿼리 최적화를 포함하여 대규모 데이터 세트를 처리하기위한 전략에 대해 설명합니다.

See all articles