or… “the case of Stewart recognizing parameters to the read() system call in strace output”.
Last week, a colleague asked a question:
I have an instance of MySQL with 100 tables and the table_definition_cache set to 1000. My understanding of this is that MySQL won’t revert to opening the FRM files to read the table definition, but we can see from strace:Shell
12345678910 [pid 19876] open("./db/t1.frm", O_RDONLY) = 32 <0.000013>[pid 19876] read(32, ""..., 10) = 10 <0.000011>[pid 19876] close(32) = 0 <0.000012>[pid 19876] open("./db/t2.frm", O_RDONLY) = 32 <0.000014>[pid 19876] read(32, ""..., 10) = 10 <0.000012>[pid 19876] close(32) = 0 <0.000012>[pid 19876] open("./db/t3.frm", O_RDONLY) = 32 <0.000014>[pid 19876] read(32, ""..., 10) = 10 <0.000011>[pid 19876] close(32) = 0 <0.000011>[pid 19876] open("./db/t4.frm", O_RDONLY) = 32 <0.000013>
So, why is this? It turns out that this triggered a memory for me from several years ago. I’ve since discovered the blog post in which I mention it: drop table fail (on the road to removing the FRM). That blog post is from 2008, almost three years ago to the day.
Since we completely reworked how metadata works in Drizzle, it has enabled us to do some truly wonderful things, including more in depth testing of the server. Amazingly enough, spin-offs from this work included being able to find out and then test that the ENUM limit of 65,535 has never been true (but now is in Drizzle), produce a CREATE TABLE statement that took over four minutes to execute and get a more complete view of how the Storage Engine API is called.
But back to what the above strace shows. In MySQL 5.5 you can find in sql/datadict.cc a function named dd_frm_type(). In MySQL 5.1, for some reason yet unknown to humans, it lives in sql/sql_view.cc as mysql_frm_type(). What this code snippet does is:
We can ignore the upper limit on number of storage engines for MySQL and understanding the relationship between the range of numbers for dynamic assignment and what this means for on-disk compatibility of data directories is left as an exercise for the reader.
This code is called from several code paths in the server:
Percona’s widely read Percona Data Performance blog highlights our expertise in enterprise-class software, support, consulting and managed services solutions for both MySQL® and MongoDB® across traditional and cloud-based platforms. The decades of experience represented by our consultants is found daily in numerous and relevant blog posts.
Besides specific database help, the blog also provides notices on upcoming events and webinars.
Want to get weekly updates listing the latest blog posts? Subscribe to our blog now! Submit your email address below.