Shulou(Shulou.com)06/01 Report--

Today, I will talk to you about the recovery of files from Anemometer BUG to FRM, which may not be well understood by many people. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

Recently, I have deeply realized that at the current rate of development, all kinds of things in the database emerge in endlessly. If I don't go to those official accounts for a week to "nourish", I will find that I don't know any new concepts.

The title is Anemometer, it is estimated that most of it is not MYSQLER. It is not clear what this is. In fact, this is a method of querying MYSQL slow query through the WEB interface a few years ago. On installation, through some scripts, you can show the slow query of each MYSQL server.

Should have been familiar with things, installed, and then each machine sent slow query statements over, in the inspection, not so complex, but a simple problem, found that the installation, does not show anything at all, in paying attention to the method installed on github and the deployment of configuration files has changed, in accordance with the way to change for a long time, or can not be displayed.

Later invited to the unit of PHP awesome people, to take a look at the PHP program, found that the BUG, found that $system_timezone can not get the correct time region, caused by specifying a time area, the Anemometer on the github began to work.

Of course, the subsequent headache is that the data entered by the PT tool is inconsistent with the structure in the database. So sometimes some open source software is only used for a period of time, and at a later stage, if the company has a strong demand, you need to consider developing a set of such things yourself.

Press the lid, the ladle, the recent MYSQL test server, because of rectification, the original settings, all the files do not have per file, but are in an ibd file, there is a problem after rectification, the data can not be read, the test data is not important, but the table structure is important for testing, developers hope to restore the table structure of MYSQL, according to the original experience The direct choice is to repair the frm file in the mysql-utilties tool collection. I thought it was very simple, but the reality is very skinny. PYTHON version 3.6 on the server, due to the operation of the replacement version of python + LINUX, I said, very stupid. In the end, even YUM is not OK, (because YUM uses PYTHON), so the end result is to find a new machine that is too clean, install mysql-utitiles in the old way, and then restore the FRM file. I was worried that this toolset had come to the end of my life (it was actually quite easy to use). When you think about it later, there is no FRM file in MYSQL 8.0, so you don't need to worry about this feature.

In addition, I recently found a project in which there is a growing demand for database selection. For example, in a requirement, if the customer strongly wants to have fuzzy queries and the demand for RDS database, then if you continue to choose ORACLE SQL SERVER, MYSQL will be a painful thing for programmers. It is obvious that such a query will cause performance problems sooner or later, if you do not understand all kinds of data. If you know the ability of POSTGRESQL, you will no doubt choose directly to reduce the cost of development and operation and maintenance. For example, the data chooses MYSQL, but the data often has an instant IN OUT peak, so analyze whether there is a mitigation method during the peak time, such as dividing MYSQL into libraries, or using REDIS + MQ to HOLD the data in the front end, and then let the database consume slowly. these are all scenarios, so separate from the business to simply talk about architecture, that's a day dream.

So I have always thought that it is very hasty to use a kind of database if you do not understand the business, and the development of the database today, the traditional relational, NO SQL, NEW SQL, in-memory database, temporal database, the choice is getting bigger and bigger, and there are more and more things you need to know.

After reading the above, do you have any further understanding of the recovery from Anemometer BUG to FRM files? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.