Жизнь, удивительные приключения и смерть бага MySQL

•

1 like•631 views

Доклад для московского MySQL Meetup 17 июня 2016 года

Жизнь, удивительные приключения и смерть
бага MySQL
Света Смирнова
Principal Technical Services Engineer
17 июня 2016 года

У багов разная судьба
∙ MySQL Bug #20786
∙ Подтверждён в 2006 году
∙ До сих пор не исправлен
∙ MySQL Bug #989
∙ Добавлена новая подсистема блокировок
∙ Закрыто 67 других багов
∙ Блог Runtime Team Lead в 2009 году
∙ MySQL Bug #23427
∙ Статус "Opened": 18 октября 2006 г.
∙ Статус "Patch pushed": 20 октября 2006 г.
2 www.percona.com

До начала работы над исправлением
Баг открыт
Это реальный баг?
В каких версиях повторяется?
Исправлен в последних версиях?
Уже зарегистрирован?
Существует ли workaround?
Verified/Confirmed
Not a Bug/
Invalid
Can’t repeat/
Invalid
Duplicate
Да
Нет
Да
Да
Да
3 www.percona.com

Расстановка приоритетов
∙ Некоторые исправления выпускаются за минуты,
другие ждут годами
∙ Обычно решения принимаются, учитывая:
∙ Насколько серьёзен баг
∙ Известное и предполагаемое количество
пользователей, которых он затронет
∙ Есть ли клиенты технической поддержки,
которым нужно исправление
∙ Сколько людей подписалось на bug report
∙ Сколько проголосовало
∙ Прямые запросы клиентов
4 www.percona.com

Как влиять на решения
∙ Не молчите
∙ Изучайте как работают баг-трекеры
∙ Открывайте заявки в техническую поддержку
5 www.percona.com

Как влиять на решения
∙ Не молчите
∙ Изучайте как работают баг-трекеры
∙ Открывайте заявки в техническую поддержку
5 www.percona.com

Спасибо!
https://bugs.launchpad.net/percona-server/
http://bugs.mysql.com/
6 www.percona.com

More Related Content

Viewers also liked

OpenSource SQL Databases Enter Millions Queries per Second Era

OpenSource SQL Databases Enter Millions Queries per Second Era

OpenSource SQL Databases Enter Millions Queries per Second Era

Percona Live 2016 (https://www.percona.com/live/data-performance-conference-2016/sessions/why-use-explain-formatjson). Although EXPLAIN FORMAT=JSON was first presented a long time ago, there still aren't many resources that explain how and why to use it. The most advertised feature is visual EXPLAIN in MySQL Workbench, but this format can do more than create nice pictures. It prints additional information that can't be found in good old tabular EXPLAIN, and can help to solve many tricky performance issues. In this session, I will not only describe which additional information we can get with the new syntax, but also provide examples showing how to use it to diagnose production issues.

Why Use EXPLAIN FORMAT=JSON?

Why Use EXPLAIN FORMAT=JSON?

Why Use EXPLAIN FORMAT=JSON?

Отладка производительности СУБД MySQL

Отладка производительности СУБД MySQL

Отладка производительности СУБД MySQL

New features in Performance Schema 5.7 in action

New features in Performance Schema 5.7 in action

New features in Performance Schema 5.7 in action

MySQL Replication Troubleshooting for Oracle DBAs

MySQL Replication Troubleshooting for Oracle DBAs

MySQL Replication Troubleshooting for Oracle DBAs

Using Apache Spark and MySQL for Data Analysis

Using Apache Spark and MySQL for Data Analysis

Using Apache Spark and MySQL for Data Analysis

Percona Live (https://www.percona.com/live/data-performance-conference-2016/sessions/performance-schema-mysql-troubleshooting) The performance schema in MySQL version 5.6, released in February, 2013, is a very powerful tool that can help DBAs discover why even the trickiest performance issues occur. Version 5.7 introduces even more instruments and tables. And while all these give you great power, you can get stuck choosing which instrument to use. In this session, I will start with a description of a typical problem, then guide you how to use the performance schema to find out what causes the issue, the reason for unwanted behavior and how the received information can help you solve a particular problem. Traditionally, performance schema sessions teach what is in contained in tables. I will, in contrast, start from a performance issue, then demonstrate which instruments and tables can help solve it. We will discuss how to setup the performance schema so that it has minimal impact on your server.

Performance Schema for MySQL Troubleshooting

Performance Schema for MySQL Troubleshooting

Performance Schema for MySQL Troubleshooting

Viewers also liked (7)

OpenSource SQL Databases Enter Millions Queries per Second Era

OpenSource SQL Databases Enter Millions Queries per Second Era

OpenSource SQL Databases Enter Millions Queries per Second Era

Why Use EXPLAIN FORMAT=JSON?

Why Use EXPLAIN FORMAT=JSON?

Why Use EXPLAIN FORMAT=JSON?

Отладка производительности СУБД MySQL

Отладка производительности СУБД MySQL

Отладка производительности СУБД MySQL

New features in Performance Schema 5.7 in action

New features in Performance Schema 5.7 in action

New features in Performance Schema 5.7 in action

MySQL Replication Troubleshooting for Oracle DBAs

MySQL Replication Troubleshooting for Oracle DBAs

MySQL Replication Troubleshooting for Oracle DBAs

Using Apache Spark and MySQL for Data Analysis

Using Apache Spark and MySQL for Data Analysis

Using Apache Spark and MySQL for Data Analysis

Performance Schema for MySQL Troubleshooting

Performance Schema for MySQL Troubleshooting

Performance Schema for MySQL Troubleshooting

More from Sveta Smirnova

25 октябрая 2023 года Oracle прекратила активную поддержку MySQL 5.7. Это значит, что стоит присмотреться к улучшениям в версии 8: - Новому системному словарю - Современному SQL - Поддержке JSON, NoSQL, MySQL Shell, и возможности работать с MySQL как с MongoDB - Улучшениям в оптимизаторе запросов и диагностике Мой доклад для разработчиков приложений под MySQL. Я не буду рассказывать как конфигурировать сервер и сфокусируюсь на его использовании.

MySQL 2024: Зачем переходить на MySQL 8, если в 5.х всё устраивает?

MySQL 2024: Зачем переходить на MySQL 8, если в 5.х всё устраивает?

MySQL 2024: Зачем переходить на MySQL 8, если в 5.х всё устраивает?

Kubernetes is the new cool in 2023. Many database installations are on Kubernetes now. And this creates challenges for Support engineers because traditional monitoring and diagnostic tools work differently on bare hardware and Kubernetes. In this session, I will focus on differences in methods we use to collect metrics, describe challenges that Percona Support hits when working with database installations on Kubernetes, and discuss how we resolve them. This talk will cover all database technologies we support: MySQL, MongoDB, and PostgreSQL. Presented at Percona Live 2023

Database in Kubernetes: Diagnostics and Monitoring

Database in Kubernetes: Diagnostics and Monitoring

Database in Kubernetes: Diagnostics and Monitoring

It is very easy to find if a database installation is having issues. You only need to enable Operating System monitoring. A disk, memory, or CPU usage change will alert you about the problems. But they would not show *why* the trouble happens. You need the help of database-specific monitoring tools. As a Support Engineer, I am always very upset when handling complaints about the database behavior lacking specific database monitoring data because I cannot help! There are two reasons database and system administrators do not enable necessary instrumentation. The first is a natural or expected performance impact. Second is the lack of knowledge on what needs to be on to resolve a particular issue. In this talk, I will cover both concerns. I will show which monitoring instruments will give information on what causes disk, memory, or CPU problems. I will teach you how to use them. I will uncover which performance impact these instruments have. I will use both MySQL command-line client and open-source graphical instrument Percona Monitoring and Management (PMM) for the examples.

MySQL Database Monitoring: Must, Good and Nice to Have

MySQL Database Monitoring: Must, Good and Nice to Have

MySQL Database Monitoring: Must, Good and Nice to Have

MySQL Cookbook 4th edition was released this summer. We are the book's authors and will show you how to "cook" MySQL. We will show you a few tasks with different priorities, such as JSON in MySQL for those who need flexibility, modern SQL for analytics, and Group Replication for high availability. We will also show how to write programs using JavaScript and Python languages, X DevAPI, and MySQL Shell. We will touch on some of the exciting features of MySQL Spatial Indexes and Geographical Data, Using a Full-Text Search, and more. We're hoping this talk will be interesting for both developers and administrators of MySQL.

MySQL Cookbook: Recipes for Developers

MySQL Cookbook: Recipes for Developers

MySQL Cookbook: Recipes for Developers

MySQL performance can be improved by tuning queries, server options, and hardware. Traditionally it was an area of responsibility for three different roles: Development, DBA, and System Administrators. Now DevOps handle these all. But there is a gap. Knowledge gained by MySQL DBAs after years or focusing on a single product is hard to gain when you focus on more than one. This is why I am doing this session. I will show a minimal but most effective set of options to improve MySQL performance. For illustrations, I will use real user stories gained from my Support experience and Percona Kubernetes operators for PXC and MySQL.

MySQL Performance for DevOps

MySQL Performance for DevOps

MySQL Performance for DevOps

Talk for TestDriven Conf: https://tdconf.ru/2022/abstracts/8763 MySQL Test Framework (MTR) — это фреймворк для регрессионных тестов MySQL. Тесты для него пишут разработчики MySQL и запускаются во время подготовки к новым релизам. MTR можно использовать и по-другому. Я его использую, чтобы тестировать проблемы, о которых сообщают клиенты, и подтверждать сообщения об ошибках (bug reports) одновременно на нескольких версиях MySQL. При помощи MTR можно: * программировать сложные развёртывания; * тестировать проблему на нескольких версиях MySQL/Percona/MariaDB-серверов при помощи одной команды; * тестировать несколько одновременных соединений; * проверять ошибки и возвращаемые значения; * работать с результатами запросов, хранимыми процедурами и внешними командами. Тест может быть запущен на любой машине с MySQL-, Percona- или MariaDB-сервером. Я покажу, как я работаю с MySQL Test Framework, и надеюсь, что вы тоже полюбите этот инструмент.

MySQL Test Framework для поддержки клиентов и верификации багов

MySQL Test Framework для поддержки клиентов и верификации багов

MySQL Test Framework для поддержки клиентов и верификации багов

These slides are for my talk at Percona Live 2022: https://sched.co/10KEo MySQL Cookbook 4th edition (https://www.target.com/p/mysql-cookbook-4th-edition-by-sveta-smirnova-alkin-tezuysal-paperback/-/A-85851771) is planned to be released this spring. I am one of the authors of the book and will show you how to "cook" MySQL. I will show you a few tasks with different priorities, such as JSON in MySQL for those who need flexibility; modern SQL for analytics, and Group Replication for high availability. I will also show how to write programs using JavaScript and Python languages, X DevAPI, and MySQL Shell. I expect this talk will be interesting for MySQL application developers.

MySQL Cookbook: Recipes for Your Business

MySQL Cookbook: Recipes for Your Business

MySQL Cookbook: Recipes for Your Business

Percona Live Online 2021 talk: https://www.percona.com/resources/videos/introduction-mysql-query-tuning-for-devops In this talk I will show how to get started with MySQL Query Tuning. I will make a short introduction into physical table structure and demonstrate how it may influence query execution time. Then we will discuss basic query tuning instruments and techniques, mainly EXPLAIN command with its latest variations. You will learn how to understand its output and how to rewrite queries or change table structure to achieve better performance.

Introduction into MySQL Query Tuning for Dev[Op]s

Introduction into MySQL Query Tuning for Dev[Op]s

Introduction into MySQL Query Tuning for Dev[Op]s

Talk for the DevOps Pro Moscow 2021: https://www.devopspro.ru/Sveta-Smirnova/ Производительность MySQL можно улучшить при помощи оптимизации запросов, настроек MySQL сервера и железа. Традиционно эти задачи распределялись между тремя ролями: Разработчик, Администратор баз данных и Системный Администратор. Теперь же все эти задачи решает DevOps, что непросто для одного человека. В этом докладе я расскажу об основных оптимизациях, которые решают большинство проблем производительности MySQL. Для иллюстраций я буду использовать реальные пользовательские истории и Percona Kubernetes Operator.

Производительность MySQL для DevOps

Производительность MySQL для DevOps

Производительность MySQL для DevOps

MySQL performance can be improved by tuning queries, server options, and hardware. Traditionally it was an area of responsibility of three different roles: Development, DBA and System Administrators. Now DevOps handle these all. But there is a gap. Knowledge, gained by MySQL DBAs after years or focus on the single product is hard to gain when you focus on more than one. This is why I am doing this session. I will show minimal, but the most effective, set of options which will improve MySQL performance. For illustrations, I will use real user stories, gained by my Support experience, and Kubernetes operators, now available from all main MySQL eco-system vendors: Oracle, MariaDB, and Percona. Presented at Open Source Summit Europe 2020: https://sched.co/eCGf

MySQL Performance for DevOps

MySQL Performance for DevOps

MySQL Performance for DevOps

Percona XtraDB Cluster (PXC) is a 100% synchronized cluster in regards to DML operations. It is ensured by the optimistic locking model and ability to rollback transaction which cannot be applied on all nodes. However, DDL operations are not transactional in MySQL. This adds complexity when you need to change the schema of the database. Changes made by DDL may affect the results of the queries. Therefore all modifications must replicate on all nodes prior to the next data access. For operations that run momentarily, it can be easily achieved, but schema changes may take hours to apply. Therefore in addition to the safest synchronous blocking schema upgrade method: TOI, - PXC supports more relaxed, though not safe, method RSU. RSU: Rolling Schema Upgrade is advertised to be non-blocking. But you still need to take care of updates, running while you are performing such an upgrade. Surprisingly, even updates on not related tables and schema can cause RSU operation to fail. In this talk, I will uncover nuances of PXC schema upgrades and point to details you need to take special care about. Further Information Schema change is a frequent task, and many do not expect any surprises with it. However, the necessity to replay the changes to all synchronized nodes adds complexity. I made a webinar on a similar topic which was recorded and available for replay. Now I have found that I share a link to the webinar to my Support customers approximately once per week. Not having a good understanding of how schema change works in the cluster leads to lockups and operation failures. This talk will provide a checklist that will help to choose the best schema change method. Presented at Percona Live Online: https://perconaliveonline2020.sched.com/event/ePm2/how-to-avoid-pitfalls-in-schema-upgrade-with-percona-xtradb-cluster

How to Avoid Pitfalls in Schema Upgrade with Percona XtraDB Cluster

How to Avoid Pitfalls in Schema Upgrade with Percona XtraDB Cluster

How to Avoid Pitfalls in Schema Upgrade with Percona XtraDB Cluster

Presented at MariaDB Server Fest 2020: https://mariadb.org/fest2020/migrate-mysql/ MariaDB is a drop-in replacement for MySQL. Initial migration is simple: start MariaDB over the old MySQL datadir. Later your application may notice that some features work differently than with MySQL. These are MariaDB improvements, so this is good and, likely the reason you migrated. In this session, I will focus on the differences affecting application performance and behavior. In particular, features sharing the same name, but working differently.

How to migrate from MySQL to MariaDB without tears

How to migrate from MySQL to MariaDB without tears

How to migrate from MySQL to MariaDB without tears

Presented at MariaDB Server Fest 2020: https://mariadb.org/fest2020/improvements/ MariaDB is famous for working well in high-performance environments. But our view of what to call high-performance changes over time. Every year we get faster data transfer speed; more devices connected to the Internet; more users and, as a result, more data. Challenges, which developers have to solve, are getting harder. This session shows what engineers do to keep the product up to date, focusing on MariaDB improvements that make it different from its predecessor, MySQL.

Modern solutions for modern database load: improvements in the latest MariaDB...

Modern solutions for modern database load: improvements in the latest MariaDB...

Modern solutions for modern database load: improvements in the latest MariaDB...

Presented at Percona MySQL Tech Day on September 10, 2020: https://www.percona.com/tech-days#mysql It is common knowledge that built-in asynchronous active-active replication is not safe. I remember times when the official MySQL User Reference Manual stated that such an installation is not recommended for production use. Some experts repeat this claim even now. While this statement is generally true, I worked with thousands of shops that successfully avoided asynchronous replication limitations in active-active setups. In this talk, I will show how they did it, demonstrate situations when asynchronous source-source replication is the best possible high availability option and beats such solutions as Galera or InnoDB Clusters. I will also cover common mistakes, leading to disasters.

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

MySQL всегда использовали под высокой нагрузкой. Недаром эта база была и остаётся самым популярным бэкэндом для web. Однако наши представления о хайлоде с каждым годом расширяются. Большая скорость передачи данных -> больше устройств с подключением к интернет -> больше пользователей -> больше данных. Задачи, стоящие перед разработчиками MySQL, с каждым годом усложняются. В этом докладе я расскажу как менялись сценарии использования MySQL за [почти] 25 лет её истории и что делали инженеры, чтобы MySQL оставалась актуальной. Мы затронем такие темы, как работа с большим количеством активных соединений и высокими объёмами данных. Я покажу насколько современные версии лучше справляются с возросшими нагрузками. Я надеюсь, что после моего доклада те слушатели, которые используют старые версии, захотят обновиться и те, кто уже обновились, узнают как использовать современный MySQL на полную мощность. Прочитана на конференции OST 2020: https://ostconf.com/materials/2857#2857

Современному хайлоду - современные решения: MySQL 8.0 и улучшения Percona

Современному хайлоду - современные решения: MySQL 8.0 и улучшения Percona

Современному хайлоду - современные решения: MySQL 8.0 и улучшения Percona

Galera Cluster for MySQL is a 100% synchronized cluster in regards to data modification operations (DML). It is ensured by the optimistic locking model and ability to rollback a transaction, which cannot be applied on all nodes. However, schema changes (DDL operations) are not transactional in MySQL, which adds complexity when you need to perform an upgrade or change schema of the database. Changes made by DDL may affect results of the queries. Therefore all modifications must replicate on all nodes prior next data access. For operations which run momentarily it can be easily achieved, but schema changes may take hours to apply. Therefore in addition to safest synchronous blocking schema upgrade method TOI Galera also supports more relaxed, thought not safe, method RSU. In her talk Sveta will describe which pitfalls you can hit while performing the change using one or another method, why and how to avoid them. Presented at MariaDB Day Brussels 0202 2020: https://mariadb.org/mariadb-day-brussels-0202-2020-provisional-schedule/

How to Avoid Pitfalls in Schema Upgrade with Galera

How to Avoid Pitfalls in Schema Upgrade with Galera

How to Avoid Pitfalls in Schema Upgrade with Galera

It is common knowledge that built-in asynchronous master-master (active-active) replication is not safe. I remember times when the official MySQL User Reference Manual stated that such an installation is not recommended for production use. Some experts repeat this claim even now. While this statement is generally true, I worked with thousands of shops that successfully avoided asynchronous replication limitations in active-active setups. In this talk, I will show how they did it, demonstrate situations when asynchronous master-master replication is the best possible high availability option and beats such solutions as Galera or InnoDB Clusters. I will also cover common mistakes, leading to disasters. Presented in "MySQL, MariaDB and Friends devroom" at Fosdem in 2020: https://fosdem.org/2020/schedule/event/mysql_master_master/

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

To get data, we query the database. MySQL does its best to return requested bytes as fast as possible. However, it needs human help to identify what is important and should be accessed in the first place. Queries, written smartly, can significantly outperform automatically generated ones. Indexes and Optimizer statistics, not limited to the Histograms only, help to increase the speed of the query a lot. In this session, I will demonstrate by examples of how MySQL query performance can be improved. I will focus on techniques, accessible by Developers and DevOps rather on those which are usually used by Database Administrators. In the end, I will present troubleshooting tools which will help you to identify why your queries do not perform. Then you could use the knowledge from the beginning of the session to improve them.

Introduction to MySQL Query Tuning for Dev[Op]s

Introduction to MySQL Query Tuning for Dev[Op]s

Introduction to MySQL Query Tuning for Dev[Op]s

We store data with an intention to use it: search, retrieve, group, sort... To do it effectively the MySQL Optimizer uses index statistics when compiles the query execution plan. This approach works excellently unless your data distribution is not even. Last year I worked on several tickets where data follow the same pattern: millions of popular products fit into a couple of categories and rest used the rest. We had a hard time to find a solution for retrieving goods fast. We offered workarounds for version 5.7. However new MariaDB and MySQL 8.0 feature: histograms, - would work better, cleaner and faster. The idea of the talk was born. Of course, histograms are not a panacea and do not help in all situations. I will discuss: how index statistics physically stored by the storage engine which data exchanged with the Optimizer why it is not enough to make correct index choice when histograms can help and when they cannot differences between MySQL and MariaDB histograms

Billion Goods in Few Categories: How Histograms Save a Life?

Billion Goods in Few Categories: How Histograms Save a Life?

Billion Goods in Few Categories: How Histograms Save a Life?

Last year this session’s speaker worked on several cases where data followed the same pattern: millions of popular products fit into a couple of categories, and the rest uses the rest. Her team had a hard time finding a solution for retrieving goods quickly. MySQL 8.0 has a feature that resolves such issues: optimizer histograms, storing statistics of an exact number of values in each data bucket. In real life, histograms don’t help with all queries accessing nonuniform data. How you write a statement, the number of rows in the table, data distribution: All of these may affect the use of histograms. This presentation shows examples demonstrating how the optimizer works in each case, describes how to create histograms, and covers differences between MySQL and Oracle implementations.

A Billion Goods in a Few Categories: When Optimizer Histograms Help and When ...

A Billion Goods in a Few Categories: When Optimizer Histograms Help and When ...

A Billion Goods in a Few Categories: When Optimizer Histograms Help and When ...

More from Sveta Smirnova (20)

MySQL 2024: Зачем переходить на MySQL 8, если в 5.х всё устраивает?

MySQL 2024: Зачем переходить на MySQL 8, если в 5.х всё устраивает?

MySQL 2024: Зачем переходить на MySQL 8, если в 5.х всё устраивает?

Database in Kubernetes: Diagnostics and Monitoring

Database in Kubernetes: Diagnostics and Monitoring

Database in Kubernetes: Diagnostics and Monitoring

MySQL Database Monitoring: Must, Good and Nice to Have

MySQL Database Monitoring: Must, Good and Nice to Have

MySQL Database Monitoring: Must, Good and Nice to Have

MySQL Cookbook: Recipes for Developers

MySQL Cookbook: Recipes for Developers

MySQL Cookbook: Recipes for Developers

MySQL Performance for DevOps

MySQL Performance for DevOps

MySQL Performance for DevOps

MySQL Test Framework для поддержки клиентов и верификации багов

MySQL Test Framework для поддержки клиентов и верификации багов

MySQL Test Framework для поддержки клиентов и верификации багов

MySQL Cookbook: Recipes for Your Business

MySQL Cookbook: Recipes for Your Business

MySQL Cookbook: Recipes for Your Business

Introduction into MySQL Query Tuning for Dev[Op]s

Introduction into MySQL Query Tuning for Dev[Op]s

Introduction into MySQL Query Tuning for Dev[Op]s

Производительность MySQL для DevOps

Производительность MySQL для DevOps

Производительность MySQL для DevOps

MySQL Performance for DevOps

MySQL Performance for DevOps

MySQL Performance for DevOps

How to Avoid Pitfalls in Schema Upgrade with Percona XtraDB Cluster

How to Avoid Pitfalls in Schema Upgrade with Percona XtraDB Cluster

How to Avoid Pitfalls in Schema Upgrade with Percona XtraDB Cluster

How to migrate from MySQL to MariaDB without tears

How to migrate from MySQL to MariaDB without tears

How to migrate from MySQL to MariaDB without tears

Modern solutions for modern database load: improvements in the latest MariaDB...

Modern solutions for modern database load: improvements in the latest MariaDB...

Modern solutions for modern database load: improvements in the latest MariaDB...

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

Современному хайлоду - современные решения: MySQL 8.0 и улучшения Percona

Современному хайлоду - современные решения: MySQL 8.0 и улучшения Percona

Современному хайлоду - современные решения: MySQL 8.0 и улучшения Percona

How to Avoid Pitfalls in Schema Upgrade with Galera

How to Avoid Pitfalls in Schema Upgrade with Galera

How to Avoid Pitfalls in Schema Upgrade with Galera

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

How Safe is Asynchronous Master-Master Setup?

Introduction to MySQL Query Tuning for Dev[Op]s

Introduction to MySQL Query Tuning for Dev[Op]s

Introduction to MySQL Query Tuning for Dev[Op]s

Billion Goods in Few Categories: How Histograms Save a Life?

Billion Goods in Few Categories: How Histograms Save a Life?

Billion Goods in Few Categories: How Histograms Save a Life?

A Billion Goods in a Few Categories: When Optimizer Histograms Help and When ...

A Billion Goods in a Few Categories: When Optimizer Histograms Help and When ...

A Billion Goods in a Few Categories: When Optimizer Histograms Help and When ...

Жизнь, удивительные приключения и смерть бага MySQL

1. Жизнь, удивительные приключения и смерть бага MySQL Света Смирнова Principal Technical Services Engineer 17 июня 2016 года

2. У багов разная судьба ∙ MySQL Bug #20786 ∙ Подтверждён в 2006 году ∙ До сих пор не исправлен ∙ MySQL Bug #989 ∙ Добавлена новая подсистема блокировок ∙ Закрыто 67 других багов ∙ Блог Runtime Team Lead в 2009 году ∙ MySQL Bug #23427 ∙ Статус "Opened": 18 октября 2006 г. ∙ Статус "Patch pushed": 20 октября 2006 г. 2 www.percona.com

3. До начала работы над исправлением Баг открыт Это реальный баг? В каких версиях повторяется? Исправлен в последних версиях? Уже зарегистрирован? Существует ли workaround? Verified/Confirmed Not a Bug/ Invalid Can’t repeat/ Invalid Duplicate Да Нет Да Да Да 3 www.percona.com

4. Расстановка приоритетов ∙ Некоторые исправления выпускаются за минуты, другие ждут годами ∙ Обычно решения принимаются, учитывая: ∙ Насколько серьёзен баг ∙ Известное и предполагаемое количество пользователей, которых он затронет ∙ Есть ли клиенты технической поддержки, которым нужно исправление ∙ Сколько людей подписалось на bug report ∙ Сколько проголосовало ∙ Прямые запросы клиентов 4 www.percona.com

5. Как влиять на решения ∙ Не молчите ∙ Изучайте как работают баг-трекеры ∙ Открывайте заявки в техническую поддержку 5 www.percona.com

6. Как влиять на решения ∙ Не молчите ∙ Изучайте как работают баг-трекеры ∙ Открывайте заявки в техническую поддержку 5 www.percona.com

7. Спасибо! https://bugs.launchpad.net/percona-server/ http://bugs.mysql.com/ 6 www.percona.com