Just upgrade and take advantage of performance improvements in PostgreSQL 12.
Version 2.28 (release notes) of the GNU C library introduces many changes to the collations it provides. Collations determine how strings are compared and by default, PostgreSQL uses the operating system’s collations which on Linux means glibC. When your operating system updates to this version of glibc and you aren't using the “C” or “POSIX” collation, you may encounter some differently ordered indexes. This unexpected change in the order of indexes will lead to incorrectly ordered query results and possible data corruption. Currently, the following distributions are affected:
One of the most important things to using PostgreSQL successfully in your development and production environments is simply getting started! One of the most popular ways to install PostgreSQL is by using RPM packages. This guide demonstrates how you can get PostgreSQL up and running with RPMs!
PostgreSQL provides a many authentications methods to allow you to pick the one that makes the most sense for your environment. This guide will show you how to use your Windows Active Directory to authenticate to PostgreSQL via GSSAPI Kerberos authentication.
Disaster recovery and backup tools like pgBackRest help ensure the high-availability of PostgreSQL, but there are cases where you do not want run them on your primary, such as due to I/O constraints or archiving a replica in another data center. This guide shows how to run pgBackRest with a replica.
Your PostgreSQL data model directly affects how much data is stored on disk. Additionally, your ingest rate and retention could affect whether you require 10TB or 100TB of storage! This deep dive can help you save orders of magnitude of disk space before using sharding or other distributed models.
Learn how to prevent transaction ID wraparound in PostgreSQL through some simple monitoring and prevent TXID wraparound from ever becoming a problem!
A guide to building an active-active PostgreSQL cluster to help meet high-availability requirements of keeping your PostgreSQL database always up and available
For most major upgrades using a utility such as pg_upgrade or a replication tool such as pglogical will be the best solution. However if these options are not available, pg_dumpall can be used to safely perform a major upgrade of your PostgreSQL database.
A practical guide to detecting if your PostgreSQL replicas are out-of-sync and how to restore them efficiently without a base backup.
Here is a case study for how to efficiently upgrade major versions of PostgreSQL with almost zero-downtime using pglogical