In a previous blog post, we discussed the installation of ProxySQL and its configuration system. In today’s post, we’ll set up ProxySQL to work in a MySQL Replication environment managed by  ClusterControl. We will take a look at the metrics it provides to a DBA, and how this data can be used to ensure smooth operations.

Why ProxySQL?

This is very valid question most of you are probably asking. You either already are using some kind of proxy layer (be it HAProxy or MaxScale perhaps), or you have concluded that you don’t really need a proxy layer in your setup. Why bother try and test another proxy? How can it help you …

If you want to get Query string value then you can get using Request Facade OR Input Facade in larave 5 But if you was working native PHP then we can get GET method we can get query string parameters in laravel 6 laravel 7 and laravel 8 applicationLets see bellow examplesIn following exa

In this blog post, we’ll discuss read-write split routing in MaxScale.

The two previous posts have shown how to setup high availability (HA) with Maxscale using asynchronous replication and how we monitor replication.

Now let’s focus on the routing module performing read-write splits.

This is our current configuration:

[Splitter Service]
type=service
router=readwritesplit
servers=percona1, percona2
max_slave_replication_lag=30
user=maxscale
passwd=264D375EC77998F13F4D0EC739AABAD4

This …

I was on the quest of searching the Holy Grail of Go programming, and I found something, which I doubt that it is, but close enough – for the first sight.

I have several problems with GO, first, that I write my code on an OSX box, and I’ll run the programs on Linux hosts, so I have to solve the cross compilation; my second problem with Go, that I don’t really like the “There is a GO project folder, and all the GO projects are relying on” approach. It makes using GitHub painful.

The first problem of mine is easily achievable since GO 1.5: we only need a GOOS environment variable and we can compile to different OS-es (see more at Dave Cheney: http://dave.cheney.net/2015/08/22/cross-compilation-with-go-1-5) easily.

The second problem is easily solvable too, just we have to start using the GOPATH variable for every GO project we have.

I don’t really want to use any external dependencies, so I decided to …

VMware Continuent provides data replication between relational databases, and to data warehouses and analytics engines. In addition, VMware Continuent provides globally redundant disaster recovery, commercial-grade high availability and performance scaling. 

To learn more, come visit us at the Percona Live Data Performance Conference, booth # 104!

If you are work on laravel 5 application and you require to get client ip address then you can get easy you dont need to use SERVER variable like native PHP but laravel 5 provide Request facade you can fetch easy using following examplestrong classexampleExamplestrongpre classpre

DNS is one of the most fundamental parts of a website. No website can run without a proper configuration on DNS. For beginners, it might be a bit difficult for them to understand and resolve DNS-related issues. This post aims to provide a bit more help for those who are still struggling to configure the DNS for their websites.

In short, what is DNS and why we need it?

DNS stands for Domain Name Service. You can think of it as a computer responsible for converting the domain name to an IP address. For example, if I type facebook.com into my browser, the DNS will look into its database and return the IP address of this domain, which is 66.220.158.68. Because of this, most of the issues about the domain name of your websites are related to DNS.

We need DNS because our human memory is limited and we cannot remember all complex and meaningless IP addresses of all websites in the world. It is just like …

Overview

DDL (Data Definition Language) statements create, alter, and remove database objects. These types of changes can be a very dangerous action to take on such a critical piece of your infrastructure. You want to make sure that the command that you are executing has been given proper thought and testing.

In this post I go through multiple version of MySQL and verify the best course of action to take in regards to executing DDL statements.  There are many things that you have to consider when making these types of changes, such as disk space, load on the database server, slave replication, the type of DDL statement you are executing, and if it will lock the table. 

Because of these risks, there are tools that can be used to help mitigate some of the dangers. But unless you have tested and verified their functionality, these tools in themselves can cause trouble. Whenever in doubt, take the time to test …

Maintaining partitioned tables in MySQL can be tedious. In a reporting database that uses monthly date partitions, I've found that I can simplify many frequent partition operations using the common_schema QueryScript language. Below I will describe two specific examples.

Removing old data

I like to keep a 2-3 month window of data in some of my reporting tables. In order to maintain that window I periodically purge data more than 3 months old using the TRUNCATE PARTITION command. Since I want to apply the same purge logic to all tables matching a consistent naming pattern, I can use the common_schema …

This blog examines MySQL 5.7’s primary key lookup results, and determines if MySQL 5.7 is really faster than its early versions.

MySQL 5.7 was released some time ago, and now that the dust has settled it’s a good time to review its performance improvements.

I’m not doing this just to satisfy my own curiosity! Many customers still running MySQL 5.6 (or even MySQL 5.5) often ask “How much performance gain we can expect by switching to 5.7? Or will it actually be a performance hit, especially after Peter’s report here: https://www.percona.com/blog/2013/02/18/is-mysql-5-6-slower-than-mysql-5-5/?”

To determine the answer, we’ll look at some …