We love supporting communities and open source. One of the things we are thrilled about at Percona is hybrid and in-person conferences coming back this fall. Local events are a perfect opportunity to meet and reinforce you, community members, and open source lovers, talk about databases and remote work, and maybe even hug! Especially for [&]

https://www.percona.com/blog/percona-sponsors-conferences-and-supports-community/

This fall we started to run live-streamed online meetups accompanied by a live chat with the audience. Every week we invite experts for a real-time talk and devote this meeting to a specific database. But the holiday season is coming soon! So, we slightly changed the meetup schedule and would like to announce it. Here [&]

https://www.percona.com/blog/community-meetup-schedule-till-the-end-of-the-year/

Centos side of things. This isn't laziness on the part of the maintainers, rather there's so much in the way of advances that it's simply not practical to maintain this technical debt for longer than a few years at a time. Best practices require the same versioned extension to be present on both source and target data clusters. Keep in mind when it comes to major version differences some extensions are more flexible than others. Otherwise, one is forced to remove it from the source data cluster if it's not present on the target. For some extensions, such as the internal ones that come bundled with the PostgreSQL packages and certain 3rd party extensions, such as pg_repack, it is possible to upgrade between extension major versions without issue. In regards to PostGIS: when faced with different extension versions between the source and target data clusters one must begin by upgrading postgis on the source data cluster such that it matches BOTH the major and minor versions of the target data cluster and only thereafter performing the PostgreSQL upgrade. Alternatively, one can install a downgraded major/minor version of PostGIS on the target data cluster, matching the source data cluster's major and minor version of PostGIS, and then upgrade PostgreSQL (yes, this is convoluted). Some cloud providers do NOT offer more than one version of PostGIS for any particular version of PostgreSQL thereby making the previous recommendation redundant. The reason is simple, they are not prepared to handle PostGIS upgrades. There are ways of dealing with them but that's for another blog. Please note that this is a rapidly moving target and can/will probably change in the future. Because the PostgreSQL community repository removes all versions of PostgreSQL and their extensions when they have reached end-of-life. PostGIS package support becomes problematic when upgrading database servers that have reached end-of-life. Over the past twenty years, I've had occasion to upgrade some fairly large installations using PostGIS, the most complex being over 120TB data on a version of PostgreSQL that hadn't been upgraded in several years and the PostGIS was so old that it wasn't even installed using extensions. As a result of this and other experiences I have, where possible, adopted the practice of performing PostGIS and PostgreSQL upgrades as separate exercises. I can't emphasize enough that regression testing for each GIS function call be made thoroughly in a development environment before going into production. Because the PostGIS project's development cycle advances at the same torrid pace as the demand for GIS, it can happen that the intrinsic behavior of a function can change seemingly without warning. Therefore, merely validating the API via a document review is insufficient, i.e. TEST IT! Here's a tip: Turn on run-time parameter track_functions and you'll be able to identify all those wonderful PostGIS functions your application stack depends upon. Finally, by all means, take a look at an earlier blog "Working with PostgreSQL and PostGIS: How To Become A GIS Expert" for more information about PostGIS." loading="lazy" style="display: block; margin-bottom: 5px; clear:both;max-width: 100%;" link_thumbnail="" srcset="https://www.percona.com/blog/wp-content/uploads/2021/11/Issues-Upgrading-PostGIS-and-PostgreSQL-200x105.png 200w, https://www.percona.com/blog/wp-content/uploads/2021/11/Issues-Upgrading-PostGIS-and-PostgreSQL-300x157.png 300w, https://www.percona.com/blog/wp-content/uploads/2021/11/Issues-Upgrading-PostGIS-and-PostgreSQL-1024x536.png 1024w, https://www.percona.com/blog/wp-content/uploads/2021/11/Issues-Upgrading-PostGIS-and-PostgreSQL-1140x595.png 1140w, https://www.percona.com/blog/wp-content/uploads/2021/11/Issues-Upgrading-PostGIS-and-PostgreSQL-367x192.png 367w, https://www.percona.com/blog/wp-content/uploads/2021/11/Issues-Upgrading-PostGIS-and-PostgreSQL.png 1200w" sizes="(max-width: 200px) 100vw, 200px" />PostGIS is arguably the best GIS implementation in the world. There may be other database technologies with GIS but the value proposition of quality, performance, and sophistication, and, of course, cost, is nowhere near what PostgreSQL offers. So let me set the stage for this blog of mine: youve been using PostGIS on your PostgreSQL [&]

https://www.percona.com/blog/issues-upgrading-postgis-and-postgresql/

Well, let me say if that happens its because there is a logic mistake in your application. But you need to know and understand what happens in MySQL to be able to avoid the problem.  In short, the WHY of this article is to inform you about possible pitfalls and how to prevent them from [&]

https://www.percona.com/blog/what-if-mysqls-repeatable-reads-cause-you-to-lose-money/

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-8-2021/

TL;DR The table below summarizes the message in this blog post. For more details and reasoning, please continue reading. What What is happening and when Percona Monitoring and Management v1 End of Life  May 2022 Percona Server for MongoDB v4.0 Percona Distribution for MongoDB v4.0 End of Life  April 2022 Packaging and support [&]

https://www.percona.com/blog/eol-pmmv1-mongo40-ubuntu1604

Since version 4.2, MongoDB provides a new interesting feature called Externally Sourced Configuration File Values. It allows administrators to specify that particular variables will have their values loaded from an external resource. The external resources that are supported, at this time, are: REST APIs, which will cause MongoDB to perform HTTP GET requests to a [&]

https://www.percona.com/blog/externally-sourced-configuration-file-values-in-mongodb/

Recently we published the first part of research comparing Graviton (ARM) with AMD and Intel CPU on AWS. In the first part, we selected general-purpose EC2 instances with the same configurations (amount of vCPU).  The main goal was to see the trend and make a general comparison of CPU types on the AWS platform only [&]

https://www.percona.com/blog/comparing-graviton-arm-performance-to-intel-and-amd-for-mysql-part-2/

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-october-25-2021/

In a previous article, I tested a new feature of MongoDB 5.0: resharding. Today, I take a look at another new feature: the Time Series collections. The Time Series collection is an astonishing new feature available in MongoDB 5.0. Based on the first tests I have done, the Time Series support provides comparable performance to [&]

https://www.percona.com/blog/mongodb-5-0-time-series-collections/

Following this series of blog posts started by Evgeniy Patlan: How to Manually Build Percona Server for MySQL RPM Packages How to Build Percona Server for MySQL From Sources well show you how to build Percona Server for MongoDB for various operating systems^1 using Docker on your local Linux machine/build server. In this very case, [&]

https://www.percona.com/blog/how-to-build-percona-server-for-mongodb-for-various-operating-systems/

The cloud-native landscape matures every day, and new great tools and products continue to appear. We are starting a series of blog posts that are going to focus on new tools in the container and cloud-native world, and provide a holistic view through the prism of Percona products. In this blog: VMware Tanzu Community edition [&]

https://www.percona.com/blog/cloud-native-series-1

Recently, AWS presented its own CPU on ARM architecture for server solutions. It was Graviton. As a result, they update some lines of their EC2 instances with new postfix “g” (e.g. m6g.small, r5g.nano, etc.). In their review and presentation, AWS showed impressive results that it is faster in some benchmarks up to 20 percent. On [&]

https://www.percona.com/blog/comparing-graviton-performance-to-arm-and-intel-for-mysql/

Percona has been named a finalist in the Computing Technology Product Awards for Best Use of Open Source Technologies. If you’re a customer, partner, or just a fan of Percona and what we stand for, we’d love your vote. With Great Power& You know the phrase. We’re leaving it to you and your peers in [&]

https://www.percona.com/blog/percona-is-a-finalist-for-best-use-of-open-source-technologies-in-2021/

A few weeks ago we did a live stream talking about Percona Monitoring and Management (PMM) and showcased some of the fun things we were doing at the OSS Summit.  During the live stream, we tried to enable some custom queries to track the number of comments being added to our movie database example.  We [&]

https://www.percona.com/blog/custom-percona-monitoring-and-management-metrics-in-mysql-and-postgresql/

This blog post is the last in the series of articles on migrating databases to Kubernetes with Percona Operators. Two previous posts can be found here: Migrating PostgreSQL to Kubernetes Migration of a MySQL Database to a Kubernetes Cluster Using Asynchronous Replication As you might have guessed already, this time we are going to cover [&]

https://www.percona.com/blog/migrating-mongodb-to-kubernetes

Often users come to us with incidents of database crashes due to OOM Killer. The Out Of Memory killer terminates PostgreSQL processes and remains the top reason for most of the PostgreSQL database crashes reported to us. There could be multiple reasons why a host machine could run out of memory, and the most common [&]

https://www.percona.com/blog/why-linux-hugepages-are-super-important-for-database-servers-a-case-with-postgresql/

ProxySQL 2.3.0 was recently released and when I was reading the release notes, I was really impressed with the Group Replication enhancements and features. I thought of experimenting with those things and was interested to write a blog about them. Here, I have focused on the following two topics: When the replication lag threshold is [&]

https://www.percona.com/blog/proxysql-2-3-0-enhanced-support-for-mysql-group-replication/

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-october-11-2021/

As per the glossary, Disaster Recovery (DR) protocols are an organization’s method of regaining access and functionality to its IT infrastructure in events like a natural disaster, cyber attack, or even business disruptions related to the COVID-19 pandemic. When we talk about data, storing backups on remote servers is enough to pass DR compliance checks [&]

https://www.percona.com/blog/disaster-recovery-for-mongodb-on-kubernetes