Google Cloud SQL中的optimizer_search_depth [英] optimizer_search_depth in Google Cloud SQL

问题描述

我的Google Cloud SQL数据库有问题.某些查询的状态长时间保持统计".

I have a problem in my Google Cloud SQL database. State of some queries stays "statistics" for long time.

+-------+------+-----------+------+---------+------+------------+--------------
| Id    | User | Host      | db   | Command | Time | State      | Info         
+-------+------+-----------+------+---------+------+------------+--------------
| 18533 | root | localhost | mydb | Execute | 2485 | statistics | SELECT * FROM...
| 18537 | root | localhost | mydb | Execute | 2424 | statistics | SELECT * FROM...
| 18539 | root | localhost | mydb | Execute | 2363 | statistics | SELECT * FROM...
| 18542 | root | localhost | mydb | Execute | 2304 | statistics | SELECT * FROM...

我阅读了此页面.而且我想更改"optimizer_search_depth"设置，但在Google开发者控制台-> Cloud SQL中找不到此设置.

I read this page. And I want to change "optimizer_search_depth" setting, but I can't find this setting in Google developer console -> Cloud SQL.

Google Cloud SQL可以更改此设置吗?如果不能，还有另一种避免长时间统计问题的方法吗?

Can Google Cloud SQL change this setting? If it can't, is there another way to avoid long statistics issue?

推荐答案

我们听说过:)我已经发出了一项更改，该更改将添加optimizer_search_depth作为用于MySQL 5.5和5.6的Cloud SQL的可配置标志.它需要经过几轮审查，但应该在下周初的某个时间发布.

We heard you :) I've sent out a change that will add optimizer_search_depth as a configurable flag for Cloud SQL for MySQL 5.5 and 5.6. It needs to go through some rounds of review, but should be available sometime early next week.

希望这对您的长时间查询有所帮助！

I hope this helps you with your long queries!

Chris，Cloud SQL团队

Chris, Cloud SQL team

这篇关于Google Cloud SQL中的optimizer_search_depth的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！