<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Performance Schema on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</title>
    <link>https://ronaldbradford.com/tags/performance-schema/</link>
    <description>Recent content in Performance Schema on Enterprise Data Architect | Principal Data Strategist |  MySQL Subject Matter Expert |  Author | Speaker</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 22 Nov 2010 13:30:58 +0000</lastBuildDate>
    <atom:link href="https://ronaldbradford.com/tags/performance-schema/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Damm you Peformance Schema</title>
      <link>https://ronaldbradford.com/blog/damm-you-peformance-schema-2010-11-22/</link>
      <pubDate>Mon, 22 Nov 2010 13:30:58 +0000</pubDate>
      <guid>https://ronaldbradford.com/blog/damm-you-peformance-schema-2010-11-22/</guid>
      <description>One significant new feature of MySQL 5.5 is the Performance Schema . I recently performed an upgrade from 5.0 to 5.5, however my check of differences in the MySQL variables via mysqladmin variables failed because we now have a new record long variable name “performance_schema_events_waits_history_long_size”.</description>
    </item>
  </channel>
</rss>
