How can we fix a nasty out-of-space issue leveraging the flexibility of Percona Operator for MySQL?

When planning a database deployment, one of the most challenging factors to consider is the amount of space we need to dedicate to data on disk.

This is even more cumbersome when working on bare metal, as it is more difficult to add space when using this kind of solution with respect to the cloud.

When using cloud storage like EBS or similar, it is normally easy(er) to extend volumes, which gives us the luxury to plan the space to allocate for data with a good grade of relaxation. 

Is this also true when using a solution based on Kubernetes like Percona Operator for MySQL? Well, it depends on where you run it. However, if the platform you choose supports the option to extend volumes, K8s per se gives you the …

How we could  fix a nasty out of space issue leveraging the flexibility of Percona MySQL operator (PMO)  

When planning a database deployment, one of the most challenging factors to consider is the amount of space we need to dedicate for Data on disk.

This is even more cumbersome when working on bare metal. Given it is definitely more difficult to add space when using this kind of solution in respect to the cloud. 

This is it, when using cloud storage like EBS or similar it is normally easy(er) to extend volumes, which gives us the luxury to plan the space to allocate for data with a good grade of relaxation. 

Is this also true when using a solution based on Kubernetes like Percona Operator for MySQL? Well it depends on where you run it, however if the platform you choose supports the option to extend volumes K8s per se is giving you the possibility to do so as well.

…

Recently Oracle released new versions of their software and there are some things of note. MySQL 8.032 is not a major change but you do need to be aware of some changes just in case they have the potential to send you into the court of Murphy’s Law. So let’s look through the release notes to see what is new, changed, and deprecated.

My own comments are in italics and reflect the views of neither Percona nor anyone else. Percona’s release of ‘32 is in the works as we have to add the features Percona provides such as enterprise features (data masking, connection pooling, RocksDB, and much more).

The following items caught my eye as either interesting or ‘I need to add this to my to-do list’.

No more leading dollar signs for table names

> CREATE TABLE $Dollar (i int);
Query OK, 0 rows affected, 1 warning (0.0192 sec)
Warning (code 1681): '$ as the first character of an unquoted identifier' is …

In this blog post, we are going to show you how to fix corrupted tables in MySQL. MySQL is an ...

Read More

The post How To Fix Corrupted Tables in MySQL appeared first on RoseHosting.

OpenLampTech is your media source for original and curated MySQL, PHP, and LAMP stack-related content. This week’s newsletter has many many great reads. Thank you for reading and making the publication a success. Please share with others!

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

This week in OpenLampTech issue #61, we have articles covering:

• Harsh realities of using Linux
• WooCommerce before and after add-to-cart hooks
• MySQL table name case
• Common PHP design patterns
• And a whole lot more

Want to …

- Read Replicas with Load Balancer
- Replication Filters
- Replication Sources Without GTIDs
- MySQL HeatWave for AWS

This presentation is just a summary of new features in MySQL HeatWave.

For a more thorough and exhaustive view please read the following:

- https://docs.oracle.com/en-us/iaas/releasenotes/services/mysql-database/

- https://dev.mysql.com/doc/relnotes/heatwave/en/

The post MySQL HeatWave Report – December 2022 update first appeared on dasini.net - Diary of a MySQL expert.

Recently, while doing a test process to examine resource usage and the time required to alter the table using pt-osc, it leads to a loss of triggers even though the –preserve-triggers option is specified. I made the decision to recreate the identical circumstance so that everyone could see it.

Test environment : 

OS: Amazon Linux 2

MySQL version: 5.7.40

pt-online-schema-change version: 3.1.0

Before digging deeper, we must first obtain the whole picture. Here is an illustration of the table’s structure.

Table structure:

This is an update for MySQL 8 Stored PSM to add the ONLY_FULL_GROUP_BY mode to the global SQL_MODE variable when it’s not set during a session. Here’s the code:

/* Drop procedure conditionally on whether it exists already. */
DROP PROCEDURE IF EXISTS set_full_group_by;

/* Reset delimter to allow semicolons to terminate statements. */
DELIMITER $$

/* Create a procedure to verify and set connection parameter. */
CREATE PROCEDURE set_full_group_by()
  LANGUAGE SQL
  NOT DETERMINISTIC
  SQL SECURITY DEFINER
  COMMENT 'Set connection parameter when not set.'
BEGIN

  /* Check whether full group by is set in the connection and
     if unset, set it in the scope of the connection. */
  IF EXISTS
    (SELECT TRUE
     WHERE NOT REGEXP_LIKE(@@SESSION.SQL_MODE,'ONLY_FULL_GROUP_BY'))
  THEN
    SET @@GLOBAL.SQL_MODE := CONCAT(@@SESSION.sql_mode,',ONLY_FULL_GROUP_BY');
  END IF;
END;
$$

/* Reset the default delimiter. */
DELIMITER ;

You can call the …

Looking at how people are using COUNT(*) and COUNT(col), it looks like most of them think they are synonyms and just use what they happen to like, while there is a substantial difference in performance and even query results. Also, we find a difference in execution on InnoDB and MyISAM engines.

NOTE: All tests were applied for MySQL version 8.0.30, and in the background, I ran every query three to five times to make sure that all of them were fully cached in the buffer pool (for InnoDB) or by the filesystem (for MyISAM).

Count function for Innodb engine:

Let’s have look at the following series of examples for InnoDB engine:

CREATE TABLE count_innodb (
  id int(10) unsigned NOT NULL AUTO_INCREMENT,
  val_with_nulls int(11) default NULL,
  val_no_null int(10) unsigned NOT NULL,
  PRIMARY KEY idx (id)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

(mysql) > select count(*) from count_innodb; …

Thank you so much for reading OpenLampTech and making it the success it is today. Wow! 600 developers reading each week! I am humbled to say the very least.

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

In OpenLampTech issue #60, we are looking at some fantastic articles covering:

• Laravel Eloquent and Query Builder tips
• Drupal’s updated CKEditor 5
• How Symfony powers Drupal
• Best SQL Editors
• WooCommerce Payment Gateways
• And much more

Want to help OpenLampTech be a success …