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
This blog post discusses the pgstattuple contrib module with regards to getting an accurate assessment of bloat in your PostgreSQL environment.
A discussion of how to configure pgAudit to use an auditing role to watch only specific objects. This is helpful when managing or supporting PostgreSQL installations.
Using pgAudit for enhanced logging and auditing of PostgreSQL
Learn about pgBackRest, and open source tool for performing PostgreSQL backup and restore in an efficient and effective way.