June 19, 2013

Post: Replication in MySQL 5.6: GTIDs benefits and limitations - Part 2

mysql> change master to master_port=10002; mysql> start slave; # And then check the number of records from the t table s1> select count(*) from t; +———-+ | countcolumn would have been useful. In our case we can check that 3ec18c45-c3ae-11e2-b986-0800272864ba is the server UUID of

Post: MySQL Query Patterns, Optimized - Webinar questions followup

columns in a compound index, then the order would matter, and it would have to match the order of columns incount the movies per production year for each kind_id. It was more efficient in this case to force MySQL

Post: Understanding the maximum number of columns in a MySQL table

sets of polls: “What is the maximum number of columns in MySQL?” and “What is the minimum maximum number of columns in MySQLnumber of columns is this: /* Hack to avoid bugs with small static rows in MySQL */ reclength=max(file->min_record

Post: Is Synchronous Replication right for your app?

In both of the above examples you can imagine plenty of concurrent clients attempting to modify the same recordnumber ofSET count = $last_count where achievement = ‘killed_troll’”; } change your schema In Example 2, above, how above moving the ‘joined’ column

Post: InnoDB Full-text Search in MySQL 5.6 (part 1)

number of code changes. In part 2 of this series, we’ll reload and reset our SEO and DIR data sets

Post: COUNT(*) vs COUNT(col)

mysql> select count(val2) from fact; +————-+ | count(val2) | +————-+ | 7340032 | +————-+ 1 row in set (0.00 sec) As this is MYISAM table MySQL has cached number of rows in

Post: Be productive with the MySQL command line

number 380166807992 1 row in set (0.41 sec) 1 row in set (1 min 0.00 sec) Log sequence number 380170274979 1 row in setmysql> select count(*) from film; +———-+ | count(*) | +———-+ | 1000 | +———-+ 1 row in set (0.00 sec) mysql> exit And now if you look at the content of

Post: MySQL Users Conference - Innodb

record format ? (static recordcount exact number ofIn MySQL 5.1+ it is also possible to fix this problem for cases when number of rows innumber of patches to make Innodb IO scheduling more aggressive which is important for serious IO subsystems. Many Innodb IO settings

Post: ANALYZE: MyISAM vs Innodb

MySQL optimizer also uses number of rows in

Post: Multi Range Read (MRR) in MySQL 5.6 and MariaDB 5.5

number of these point primary key lookups will be depend on the number of rows that match the condition ‘key_columnof a bug in MySQL 5.6 code? As MRR was used in both MySQL 5.6 and MariaDB 5.5. Handler_mrr_rowid_refills counts