Percona Distribution for PostgreSQL Operator allows you to deploy and manage highly available and production-grade PostgreSQL clusters on Kubernetes with minimal manual effort. In this blog post, we are going to look deeper into High Availability, Disaster Recovery, and Scaling of PostgreSQL clusters. High Availability Our default custom resource manifest deploys a highly available (HA) [&]

https://www.percona.com/blog/postgresql-high-availability-and-disaster-recovery-on-kubernetes

Percona XtraDB Cluster 8.0.25 (PXC) has introduced a new option to perform online schema modifications: NBO (Non-Blocking Operation). When using PXC, the cluster relies on the wsrep_OSU_method parameter to define the Online Schema Upgrade (OSU) method the node uses to replicate DDL statements.  Until now, we normally have three options: Use Total Isolation Order (TOI, [&]

https://www.percona.com/blog/percona-xtradb-cluster-non-blocking-operation-for-online-schema-upgrade/

We have a quickstart guide for how to install Percona Distribution for MySQL Operator on minikube. Installing the minimal version works well as it is described in the guide. After that, we will have one HAproxy and one Percona XtraDB Cluster (PXC) node to work with. Minikube provides Kubernetes locally. One can try using the [&]

https://www.percona.com/blog/testing-percona-distribution-for-mysql-operator-locally-with-kind/

We are thrilled to announce the Percona Platform, which brings together database distributions, support expertise, services, management, and automated insights into a single product. Building on our expertise with databases including MySQL, PostgreSQL, and MongoDB, the new Percona Platform will simplify how you can monitor, manage, and optimize your database instances across any infrastructure. In [&]

https://www.percona.com/blog/a-new-way-to-experience-databases-the-percona-platform/

Percona in 2021 is heavily invested in making the PostgreSQL ecosystem better and contributing to it from different angles: We have created pg_stat_monitor  query performance monitoring tool for PostgreSQL Percona Distribution for PostgreSQL Operator was released in October Greatly improved PostgreSQL monitoring with Percona Monitoring and Management At PGConf NYC 2021 we were a [&]

https://www.percona.com/blog/postgresql-operator-110-notable-features

While we prepare to enter 2022 and start to sum up its results and schedule a plan for the future, let’s look back at the awesome posts published in the Percona Blog and find out which products and themes raised more engagement among readers. We count the number of views of each blog post and [&]

https://www.percona.com/blog/perconas-2021-most-popular-posts-on-open-source-database-technologies/

Its release roundup time again here at Percona! Percona is a leading provider of unbiased open source database solutions that allow organizations to easily, securely, and affordably maintain business agility, minimize risks, and stay competitive. Our Release Roundups showcase the latest Percona software updates, tools, and features to help you manage and deploy our software. [&]

https://www.percona.com/blog/release-roundup-december-6-2021/

For a long time, MyDumper has been in Max Bubenicks personal GitHub repository. Now, we decided to move to a new MyDumper’s Organization as requested earlier this year by a user from the community. There were also two other reasons why we decided to move it. The first one is related to how the project [&]

https://www.percona.com/blog/mydumper-github-repository-is-now-an-organization/

First, I want to thank everyone who attended my November 9, 2021 webinar “Introduction to MySQL Query Tuning for Dev[Op]s“. Recording and slides are available on our webinars page. Here are answers to the questions from participants which I was not able to provide during the webinar due to a technical issue we experienced at [&]

https://www.percona.com/blog/qa-on-the-webinar-introduction-to-mysql-query-tuning-for-devops/

Working on a real case scenario in a five node Percona XtraDB Cluster (PXC), we were forced to use wsrep_sync_wait = 1, because the app does reads-after-write and we send reads to all the nodes. We had the idea to leave some nodes in DESYNC mode to reduce the flow control messages during peak load [&]

https://www.percona.com/blog/pxc-scheduler-handler-the-missing-piece-for-galera-percona-xtradb-cluster-puzzle/

PostgreSQL-14 was released in September 2021, and it contained many performance improvements and feature enhancements, including some features from a monitoring perspective. As we know, monitoring is the key element of any database management system, and PostgreSQL keeps updating and enhancing the monitoring capabilities. Here are some key ones in PostgreSQL-14. Query Identifier Query identifier [&]

https://www.percona.com/blog/postgresql-14-database-monitoring-and-logging-enhancements/

The new MyDumper 0.11.3 version, which includes many new features and bug fixes, is now available.  You can download the code from here. We are very proud to announce that we were able to achieve the two main objectives for the milestone ZSTD and Stream support!  We added four packages with ZSTD support because not [&]

https://www.percona.com/blog/mydumper-0-11-3-is-now-available/

Here at Percona, we operate on the premise that full transparency makes a product better. We strive to build the best open-source database products, but also to help you manage any issues that arise in any of the databases that we support. And, in true open source form, report back on any issues or bugs [&]

https://www.percona.com/blog/percona-monthly-bug-report-november-2021/

A recommendation we often give to our customers is along the lines of archive old data to reduce your database size. There is a tradeoff between keeping all our data online and archiving part of it to cold storage. There could also be legal requirements to keep certain data online, or you might want to [&]

https://www.percona.com/blog/querying-archived-rds-data-directly-from-an-s3-bucket/

There are cases where multiple teams, customers, or applications run in the same Kubernetes cluster. Such an environment is called multi-tenant and requires some preparation and management. Multi-tenant Kubernetes deployment allows you to utilize the economy of scale model on various levels: Smaller compute footprint  one control plane, dense container deployments Ease of management [&]

https://www.percona.com/blog/multi-tenant-kubernetes-cluster-with-percona-operators

My last blog introduced the issues one can face when upgrading PostGIS and PostgreSQL at the same time. The purpose of this blog is to walk through the steps with an example. For our purposes, we will confine ourselves to working with the community versions of 9.6 and 11 respectively, and use LXD in order [&]

https://www.percona.com/blog/upgrading-postgis-a-proof-of-concept/

If you ever had to deal with performance and/or disk space issues related to temporary tables, I bet you eventually found yourself puzzled. There are many possible scenarios depending on the type of temporary table, settings, and MySQL version used. We have observed a pretty long evolution in that matter due to a couple of [&]

https://www.percona.com/blog/temporary-tables-in-mysql-never-ending-story/

Its release roundup time again here at Percona! Percona is a leading provider of unbiased open source database solutions that allow organizations to easily, securely, and affordably maintain business agility, minimize risks, and stay competitive. Our Release Roundups showcase the latest Percona software updates, tools, and features to help you manage and deploy our software. [&]

https://www.percona.com/blog/release-roundup-november-22-2021/

Welcome to a weekly blog where I get to answer (like, really answer) some of the questions I’ve seen in the webinars I’ve presented lately. If you missed the latest one, PostgreSQL Performance Tuning Secrets, it might be helpful to give some of it a listen before or after you read this post. Each week, [&]

https://www.percona.com/blog/should-i-create-an-index-on-foreign-keys-in-postgresql/

MySQL stores active table descriptors in a special memory buffer called the table open cache. This buffer is controlled by configuration variables table_open_cache that hold the maximum number of table descriptors that MySQL should store in the cache, and table_open_cache_instances that stores the number of the table cache instances. With default values of table_open_cache=4000 and [&]

https://www.percona.com/blog/how-triggers-may-significantly-affect-the-amount-of-memory-allocated-to-your-mysql-server/