blocks|key|4574994|text|mysql_upgrade也适用于我：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4574995|#+mysql_upgrade+-u+root+-p+--force
#+systemctl+restart+mysqld|code-block|syntax|javascript|4574996|你好，MSz。|4574997|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The mysql_upgrade worked for me as well:

<pre><code># mysql_upgrade -u root -p --force
# systemctl restart mysqld
</code></pre>

Regards,
MSz.

blocks|key|72590|text|在运行@robregonm建议的命令之后，我能够登录到mysql服务器：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|72591|mysql_upgrade+-u+root+-p+--force|code-block|syntax|javascript|72592|需要重新启动MySQL服务器。|72593|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I was able to log on to the mysql server after running the command @robregonm suggested:

<pre><code>mysql_upgrade -u root -p --force
</code></pre>

A MySQL server restart is required.

blocks|key|72610|text|mysql+-u+app+-p
mysql>+set+@@global.show_compatibility_56=ON;|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|72611|按照http://bugs.mysql.com/bug.php?id=78159的说法，他为我工作。|unstyled|offset|length|72612|entityMap|0|LINK|mutability|MUTABLE|url|http://bugs.mysql.com/bug.php?id=78159^0|0|2|12|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|R|8|@]|9|@$G|S|H|T|1|U]]|A|$]]|$1|I|3|-4|5|F|7|V|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]]]

<pre><code>mysql -u app -p
mysql&gt; set @@global.show_compatibility_56=ON;
</code></pre>

as per <a href="http://bugs.mysql.com/bug.php?id=78159">http://bugs.mysql.com/bug.php?id=78159</a> worked for me.

blocks|key|72665|text|由于上面的答案中没有一个真正解释了发生了什么，所以我决定加入进来，给这个问题带来更多的细节。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|72666|是的，解决方案是运行MySQL升级命令，如下所示：mysql_upgrade+-u+root+-p+--force，但是发生了什么？|offset|length|style|CODE|72667|造成这一问题的根本原因是performance_schema的损坏，其原因可能是：|72668|有机的损坏(卷到kaboom，引擎错误，内核驱动程序问题等)|unordered-list-item|72669|mysql期间的损坏(在mysql修补程序(特别是主要版本升级)中发生这种情况并非闻所未闻)|72670|一个简单的"drop数据库performance_schema“显然会导致这个问题，并且它会出现相同的症状，就像它被破坏了一样。|72671|这个问题甚至在修补程序之前就已经出现在您的数据库中了，但是在MySQL+5.7.8上发生的具体情况是，标志show_compatibility_56将其默认值从默认的ON改为OFF。此标志控制引擎在各种MySQL版本上设置和读取变量(会话和全局)的查询时的行为。|72672|因为MySQL+5.7%2B开始在performance_schema上而不是在information_schema上读取和存储这些变量，所以在第一个版本中引入了这个标志作为ON，以减少这种更改的爆炸半径，并让用户知道并适应它。|72673|好吧，但是为什么连接会失败呢？因为根据您所使用的驱动程序(以及它的配置)，它可能会为每个启动到数据库的新连接运行命令(例如，show+variables+)。因为其中一个命令可以尝试访问损坏的performance_schema，所以整个连接在完全启动之前会中止。|72674|因此，总之，您可能(现在不可能知道)在修补之前已经丢失或损坏了performance_schema。然后，这个5.7.8的补丁迫使引擎从performance_schema中读取变量(而不是information_schema，它是从那里读取的，因为标志被转换为ON)。由于performance_schema已损坏，连接正在失败。|72675|运行MySQL升级是最好的方法，尽管停机。打开标志是一种选择，但它有自己的一套含义，就像在这个线程上已经指出的那样。|72676|两者都应该起作用，但要权衡后果，并知道你的选择:)|72677|entityMap^0|0|P|W|0|C|I|0|0|0|0|1H|L|2B|2|2F|3|0|F|I|12|I|2D|2|0|1Q|E|2O|I|0|V|I|1W|I|2N|I|3N|2|3T|I|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@$D|19|E|1A|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|1C|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|1D|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@$D|1F|E|1G|F|G]|$D|1H|E|1I|F|G]|$D|1J|E|1K|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1L|8|@$D|1M|E|1N|F|G]|$D|1O|E|1P|F|G]|$D|1Q|E|1R|F|G]]|9|@]|A|$]]|$1|U|3|V|5|6|7|1S|8|@$D|1T|E|1U|F|G]|$D|1V|E|1W|F|G]]|9|@]|A|$]]|$1|W|3|X|5|6|7|1X|8|@$D|1Y|E|1Z|F|G]|$D|20|E|21|F|G]|$D|22|E|23|F|G]|$D|24|E|25|F|G]|$D|26|E|27|F|G]]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|28|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|29|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2A|8|@]|9|@]|A|$]]]|13|$]]

Since none of the answers above actually explain what happened, I decided to chime in and bring some more details to this issue.

Yes, the solution is to run the MySQL Upgrade command, as follows: <code>mysql_upgrade -u root -p --force</code>, but what happened?

The root cause for this issue is the corruption of <code>performance_schema</code>, which can be caused by:

<ul>
<li>Organic corruption (volumes going kaboom, engine bug, kernel driver issue etc)</li>
<li>Corruption during mysql Patch (it is not unheard to have this happen during a mysql patch, specially for major version upgrades)</li>
<li>A simple "drop database performance_schema" will obviously cause this issue, and it will present the same symptoms as if it was corrupted</li>
</ul>

This issue might have been present on your database even before the patch, but what happened on MySQL 5.7.8 specifically is that the flag <code>show_compatibility_56</code> changed its default value from being turned <code>ON</code> by default, to <code>OFF</code>. This flag controls how the engine behaves on queries for setting and reading variables (session and global) on various MySQL Versions. 

Because MySQL 5.7+ started to read and store these variables on <code>performance_schema</code> instead of on <code>information_schema</code>, this flag was introduced as <code>ON</code> for the first releases to reduce the blast radius of this change and to let users know about the change and get used to it.

OK, but why does the connection fail? Because depending on the driver you are using (and its configuration), it may end up running commands for every new connection initiated to the database (like <code>show variables</code>, for instance). Because one of these commands can try to access a corrupted <code>performance_schema</code>, the whole connection aborts before being fully initiated.

So, in summary, you may (it's impossible to tell now) have had <code>performance_schema</code> either missing or corrupted before patching. The patch to 5.7.8 then forced the engine to read your variables out of <code>performance_schema</code> (instead of <code>information_schema</code>, where it was reading it from because of the flag being turned <code>ON</code>). Since <code>performance_schema</code> was corrupted, the connections are failing.

Running MySQL upgrade is the best approach, despite the downtime. Turning the flag on is one option, but it comes with its own set of implications as it was pointed out on this thread already.

Both should work, but weight the consequences and know your choices :)

blocks|key|72642|text|在不使用-p的情况下执行以下步骤：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|72643|mysql_upgrade+-u+root|ordered-list-item|72644|systemctl+restart+mysqld|72645|我也有同样的问题，而且成功了！|72646|entityMap^0|4|2|0|0|L|0|0|O|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|I|3|J|5|H|7|U|8|@$9|V|A|W|B|C]]|D|@]|E|$]]|$1|K|3|L|5|6|7|X|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|N|$]]

Follow these steps without <code>-p</code> : 

<ol>
<li><code>mysql_upgrade -u root</code></li>
<li><code>systemctl restart mysqld</code></li>
</ol>

I had the same problem and it works!

blocks|key|4575018|text|作为sixty4bit问题，如果您的mysql根用户看起来配置错误，请尝试从mysql官方源安装配置器扩展：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4575019|https://dev.mysql.com/downloads/repo/apt/|offset|length|4575020|它将帮助您设置一个新的根用户密码。|4575021|确保更新您的存储库(debian/ubuntu)：|4575022|apt-get+update|code-block|syntax|javascript|4575023|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|15|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|11|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|12|8|@]|9|@]|A|$M|N]]|$1|O|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|C]]]]

As sixty4bit question, if your mysql root user looks to be misconfigured, try to install the configurator extension from mysql official source:

<a href="https://dev.mysql.com/downloads/repo/apt/" rel="nofollow">https://dev.mysql.com/downloads/repo/apt/</a>

It will help you to set up a new root user password.

Make sure to update your repository (debian/ubuntu) :

<pre><code>apt-get update
</code></pre>

blocks|key|4242238|text|如果在使用mysql_upgrade+-u+root+-p+--force命令时出现以下错误：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4242239|Could+not+create+the+upgrade+info+file+'/var/lib/mysql/mysql_upgrade_info'+in+the+MySQL+Servers+datadir,+errno:+13|code-block|syntax|javascript|4242240|只需在命令之前添加sudo即可。这对我有效，我解决了我的问题。所以，它是：sudo+mysql_upgrade+-u+root+-p+--force+:)|4242241|entityMap^0|5|W|0|0|9|4|11|11|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

If, while using the <code>mysql_upgrade -u root -p --force</code> command You get this error:

<pre><code>Could not create the upgrade info file '/var/lib/mysql/mysql_upgrade_info' in the MySQL Servers datadir, errno: 13
</code></pre>

just add the <code>sudo</code> before the command. That worked for me, and I solved my problem. So, it's: <code>sudo mysql_upgrade -u root -p --force</code> :)

blocks|key|4575140|text|对于我的系统来说，问题是我仍然安装了MySQL5.6，所以从安装到的mysql_upgrade.exe被调用，而不是5.7。导航到C:\Program+Files\MySQL\MySQL+Server+5.7\bin并运行.\mysql_upgrade.exe+-u+root|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4575141|entityMap^0|1T|17|33|R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

For my system the problem ended up being that I still had Mysql 5.6 installed and so the mysql_upgrade.exe from that installation was being called instead of the one for 5.7. Navigate to <code>C:\Program Files\MySQL\MySQL Server 5.7\bin</code> and run <code>.\mysql_upgrade.exe -u root</code>

blocks|key|4575047|text|有时候mysql_upgrade+-u+root+-p+--force不够真实，|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4575048|请参考以下问题：variables'+doesn't+exist|4575049|根据该计划：|4575050|开放cmd|ordered-list-item|4575051|cd+[installation_path]\eds-binaries\dbserver\mysql5711x86x160420141510\bin|4575052|mysql_upgrade+-u+root+-p+--force|4575053|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/36746677/table-performance-schema-session-variables-doesnt-exist^0|3|W|0|8|O|0|0|0|0|0|22|0|0|W|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|H|3|I|5|6|7|15|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|16|8|@]|D|@]|E|$]]|$1|M|3|N|5|L|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|O|3|P|5|L|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1D|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

sometimes <code>mysql_upgrade -u root -p --force</code> is not realy enough,

please refer to this question : <a href="https://stackoverflow.com/questions/36746677/table-performance-schema-session-variables-doesnt-exist">Table &#39;performance_schema.session_variables&#39; doesn&#39;t exist</a>

according to it: 

<ol>
<li>open cmd</li>
<li><code>cd [installation_path]\eds-binaries\dbserver\mysql5711x86x160420141510\bin</code></li>
<li><code>mysql_upgrade -u root -p --force</code></li>
</ol>

After upgrading MySQL to 5.7.8-rc
and loging to server I got error:

<pre><code>Table 'performance_schema.session_variables' doesn't exist
</code></pre>

I can't find any solution for this. Can you help ?

Table 'performance_schema.session_variables' doesn't exist

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在将MySQL升级到5.7.8-rc并登录到服务器后，我得到了错误：Table 'performance_schema.session_variables' doesn't exist我找不到任何解决办法。你能帮忙吗？

问表'performance_schema.session_variables‘不存在
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问表'performance_schema.session_variables‘不存在EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问表'performance_schema.session_variables‘不存在
EN