Thu, 11 Apr 2024 22:44:28 +0000 en-US hourly 1 https://wordpress.org/?v=6.5.2 https://www.percona.com/blog/wp-content/uploads/2023/02/cropped-percona-favicon-32x32.png 32 32 76301791 https://www.percona.com/blog/using-huge-pages-with-postgresql-running-inside-kubernetes/ https://www.percona.com/blog/using-huge-pages-with-postgresql-running-inside-kubernetes/#respond Wed, 20 Dec 2023 16:49:58 +0000 https://www.percona.com/blog/?p=92436 Huge pages make PostgreSQL faster; can we implement it in Kubernetes? Modern servers operate with terabytes of RAM, and by default, processors work with virtual memory address translation for each 4KB page. OS maintains a huge list of allocated and free pages to make slow but reliable address translation from virtual to physical.Please check out […]]]> https://www.percona.com/blog/using-huge-pages-with-postgresql-running-inside-kubernetes/feed/ 0 92436 https://www.percona.com/blog/store-and-manage-logs-of-percona-operator-pods-with-pmm-and-grafana-loki/ https://www.percona.com/blog/store-and-manage-logs-of-percona-operator-pods-with-pmm-and-grafana-loki/#respond Tue, 24 May 2022 12:55:51 +0000 https://www.percona.com/blog/?p=80993 While it is convenient to view the log of MySQL or MongoDB pods with [crayon-664c873b6f4e3855156911-i/], sometimes the log is purged when the pod is deleted, which makes searching historical logs a bit difficult. Grafana Loki, an aggregation logging tool from Grafana, can be installed in the existing Kubernetes environment to help store historical logs and […]]]> https://www.percona.com/blog/store-and-manage-logs-of-percona-operator-pods-with-pmm-and-grafana-loki/feed/ 0 80993 https://www.percona.com/blog/deploying-any-version-of-leading-open-source-databases-for-tests-and-experiments/ Wed, 27 Jan 2021 13:57:00 +0000 https://www.percona.com/blog/?p=73952 I want to present a tool for running a specific version of open source databases in a single instance, replication setups, and Kubernetes. AnyDbVer deploys MySQL/MariaDB/MongoDB/PostgreSQL for testing and experiments.It Could Be Started By…Docker (or Podman) or dbdeployer (MySQL-Sandbox successor) could also start a specific database version, but such installations are significantly different from production […]]]> 73952 https://www.percona.com/blog/fast-upgrade-of-legacy-postgresql-with-minimum-downtime-using-pg_upgrade/ https://www.percona.com/blog/fast-upgrade-of-legacy-postgresql-with-minimum-downtime-using-pg_upgrade/#comments Fri, 12 Apr 2019 15:44:44 +0000 https://www.percona.com/blog/?p=56295 When you need to upgrade your PostgreSQL databases, there are a number of options available to you. In this post we’ll take a look at how you can upgrade PostgreSQL versions using pg_upgrade, a built-in tool that allows in-place upgrade of your software. Using pg_upgrade allows you, potentially, to minimize your downtime, an essential consideration […]]]> https://www.percona.com/blog/fast-upgrade-of-legacy-postgresql-with-minimum-downtime-using-pg_upgrade/feed/ 7 56295 https://www.percona.com/blog/continuous-replication-from-legacy-postgresql-version-using-slony/ Tue, 09 Apr 2019 15:44:40 +0000 https://www.percona.com/blog/?p=56257 Native streaming replication in PostgreSQL works only between servers running the same major version. We discussed about logical replication in our previous blog post. In that post, we saw how logical replication could help us set up migration between two different PostgreSQL versions. However, logical replication works only for the currently supported versions of PostgreSQL, […]]]> 56257 https://www.percona.com/blog/replication-between-postgresql-versions-using-logical-replication/ https://www.percona.com/blog/replication-between-postgresql-versions-using-logical-replication/#comments Thu, 04 Apr 2019 17:21:11 +0000 https://www.percona.com/blog/?p=56174 When you need to upgrade PostgreSQL, there are a variety of approaches that you can use. To avoid application downtime, then not all of the options to upgrade postgres are suitable. When avoiding downtime is essential, then you might consider using replication as a means of upgrade, and depending on your scenario, you can choose […]]]> https://www.percona.com/blog/replication-between-postgresql-versions-using-logical-replication/feed/ 4 56174 https://www.percona.com/blog/postgresql-upgrade-using-pg_dump-pg_restore/ https://www.percona.com/blog/postgresql-upgrade-using-pg_dump-pg_restore/#comments Wed, 27 Mar 2019 18:09:33 +0000 https://www.percona.com/blog/?p=56089 In this blog post, we will explore  [crayon-664c873b72921755943372-i/] / [crayon-664c873b72927065717748-i/], one of the most commonly used options for performing a PostgreSQL upgrade. It is important to understand the scenarios under which [crayon-664c873b72929548351194-i/] and [crayon-664c873b7292a496907243-i/] utilities will be helpful.This post is the second of our Upgrading or Migrating Your Legacy PostgreSQL to Newer PostgreSQL Versions series […]]]> https://www.percona.com/blog/postgresql-upgrade-using-pg_dump-pg_restore/feed/ 3 56089 https://www.percona.com/blog/postgresql-upgrade-using-pg_dumpall/ Mon, 18 Mar 2019 14:59:50 +0000 https://www.percona.com/blog/?p=55856 There are several approaches to assess when you need to upgrade PostgreSQL. In this blog post, we look at the option for upgrading a postgres database using pg_dumpall. As this tool can also be used to back up PostgreSQL clusters, then it is a valid option for upgrading a cluster too. We consider the advantages […]]]> 55856 https://www.percona.com/blog/postgresql-webinar-wed-april-17-upgrading-migrating-legacy-postgresql-newer-versions/ https://www.percona.com/blog/postgresql-webinar-wed-april-17-upgrading-migrating-legacy-postgresql-newer-versions/#comments Mon, 04 Mar 2019 14:34:52 +0000 https://www.percona.com/blog/?p=55705 A date for your diary. On Wednesday, April 17 at 7:00 AM PDT (UTC-7) / 10:00 AM EDT (UTC-4) Percona’s PostgreSQL Support Technical Lead, Avinash Vallarapu and Senior Support Engineers, Fernando Laudares, Jobin Augustine and Nickolay Ihalainen, will demonstrate the upgrade of a legacy version of PostgreSQL to a newer version, using built-in as well as […]]]> https://www.percona.com/blog/postgresql-webinar-wed-april-17-upgrading-migrating-legacy-postgresql-newer-versions/feed/ 1 55705 https://www.percona.com/blog/parallel-queries-in-postgresql/ Thu, 21 Feb 2019 14:05:21 +0000 https://www.percona.com/blog/?p=54587 Modern CPU models have a huge number of cores. For many years, applications have been sending queries in parallel to databases. Where there are reporting queries that deal with many table rows, the ability for a query to use multiple CPUs helps us with a faster execution. Parallel queries in PostgreSQL allow us to utilize […]]]> 54587 https://www.percona.com/blog/postgresql-streaming-physical-replication-with-slots/ https://www.percona.com/blog/postgresql-streaming-physical-replication-with-slots/#comments Fri, 30 Nov 2018 17:05:32 +0000 https://www.percona.com/blog/?p=53981 PostgreSQL streaming physical replication with slots simplifies setup and maintenance procedures. Usually, you should estimate disk usage for the Write Ahead Log (WAL) and provide appropriate limitation to the number of segments and setup of the WAL archive procedure. In this article, you will see how to use replication with slots and understand what problems it […]]]> https://www.percona.com/blog/postgresql-streaming-physical-replication-with-slots/feed/ 1 53981 https://www.percona.com/blog/postgresql-locking-part-3-lightweight-locks/ Tue, 30 Oct 2018 13:31:40 +0000 https://www.percona.com/blog/?p=53115 PostgreSQL lightweight locks, or LWLocks, control memory access. PostgreSQL uses multi-process architecture and should allow only consistent reads and writes to shared memory structures. LWLocks have two levels of locking: shared and exclusive. It’s also possible to release all acquired LWLocks to simplify clean up. Other databases often call primitives similar to LWLocks “latches”. Because […]]]> 53115 https://www.percona.com/blog/postgresql-locking-part-2-heavyweight-locks/ Wed, 24 Oct 2018 11:39:16 +0000 https://www.percona.com/blog/?p=53113 PostgreSQL locking visibility for application developers and DBAs is in most cases related to heavyweight locks. Complex database locking operations require full instrumentation using views from the system catalog. It should be clear which object is locked by a specific database “backend” process. An alternative name for any lock is “bottleneck”. In order to make […]]]> 53113 https://www.percona.com/blog/postgresql-locking-part-1-row-locks/ Tue, 16 Oct 2018 14:26:00 +0000 https://www.percona.com/blog/?p=53028 An understanding of PostgreSQL locking is important to build scalable applications and avoid downtime. Modern computers and servers have many CPU cores and it’s possible to execute multiple queries in parallel. Databases containing many consistent structures with changes made by queries or background processes running in parallel could crash a database or even corrupt data. […]]]> 53028 https://www.percona.com/blog/keep-sensitive-data-secure-in-replication-setup/ https://www.percona.com/blog/keep-sensitive-data-secure-in-replication-setup/#comments Mon, 30 Apr 2018 21:47:29 +0000 https://www.percona.com/blog/?p=49232 This blog post describes how to keep sensitive data secure on slave servers in a MySQL async replication setup.Almost every web application has a sensitive data: passwords, SNN, credit cards, emails, etc. Splitting the database to secure and “public” parts allows for restricting user and application parts access to sensitive data. Field encryptionThis is based on […]]]> https://www.percona.com/blog/keep-sensitive-data-secure-in-replication-setup/feed/ 3 49232 https://www.percona.com/blog/restore-mysql-logical-backup-maximum-speed/ https://www.percona.com/blog/restore-mysql-logical-backup-maximum-speed/#comments Fri, 23 Feb 2018 00:35:56 +0000 https://www.percona.com/blog/?p=47448 The ability to restore MySQL logical backups is a significant part of disaster recovery procedures. It’s a last line of defense.Even if you lost all data from a production server, physical backups (data files snapshot created with an offline copy or with Percona XtraBackup) could show the same internal database structure corruption as in production […]]]> https://www.percona.com/blog/restore-mysql-logical-backup-maximum-speed/feed/ 3 47448 https://www.percona.com/blog/collect-postgresql-metrics-with-percona-monitoring-and-management-pmm/ https://www.percona.com/blog/collect-postgresql-metrics-with-percona-monitoring-and-management-pmm/#comments Fri, 09 Feb 2018 23:17:47 +0000 https://www.percona.com/blog/?p=47136 In this article, we’ll describe how to collect PostgreSQL metrics with Percona Monitoring and Management (PMM).We designed Percona Monitoring and Management (PMM) to be the best tool for MySQL and MongoDB performance investigation. At the same time, it’s built on mature opensource components: Prometheus’ time series database and Grafana. Starting from PMM 1.4.0. it’s possible to add […]]]> https://www.percona.com/blog/collect-postgresql-metrics-with-percona-monitoring-and-management-pmm/feed/ 2 47136 https://www.percona.com/blog/how-to-move-the-innodb-log-sequence-number-lsn-forward/ https://www.percona.com/blog/how-to-move-the-innodb-log-sequence-number-lsn-forward/#comments Wed, 11 Sep 2013 05:00:53 +0000 https://www.percona.com/blog/?p=17628 This post focuses on the problem of the InnoDB log sequence number being in the future.Preface: What is an InnoDB log sequence number?The log sequence number (LSN) is an important database parameter used by InnoDB in many places. The most important use is for crash recovery and buffer pool purge control.Internally, the InnoDB LSN counter never […]]]> https://www.percona.com/blog/how-to-move-the-innodb-log-sequence-number-lsn-forward/feed/ 7 17628