When should you be alerted about issues in your PostgreSQL clusters? How do you troubleshoot them? What are some typical solutions?
What are some PostgreSQL monitoring stats that are typically used to monitor the health of your databases?
What are some of the key stats to look at to ensure your PostgreSQL cluster is healthy? How can you use this stats to diagnose the problem?
PostgreSQL 13 was released last week. I'm excited about this one, as the more mature partitioning plus logical replication features allow some long-requested deployment architectures
Backups are a key staple of running any database. pgBackRest aims to be a fast, reliable, easy-to-use backup and restore solution with the ability to seamlessly scale to the largest databases.
Creation and clean up of WAL files in the primary's pg_wal folder (pg_xlog prior to PG10) is a normal part of PostgreSQL operation. The WAL files on the primary are used to ensure data consistency during crash recovery. Use of write-ahead logs (also called redo logs or transaction logs in other products) is common for data stores that must provide durability and consistency of data when writing to storage. The same technique is used in modern journaling and log-structured filesystems.
A well tuned production Postgres database is capable of easily running thousands or up to hundreds of thousands of queries per second on a beefy instance.
Learn the top 5 settings to tune once an install of PostgreSQL is completed to optimize performance.
Learn how to migrate PostgreSQL partitions that use triggers/inheritance/constraints to partitions to the native implementation in PostgreSQL 11 and above.
Learn how to deploy PostgreSQL on Kubernetes with synchronous replication to guard against losing transactions.
Migrating from one database to another is inherently new technology and can raise a multitude of questions.
In order to more easily monitor PgBouncer, the team at Crunchy Data developed an open source PgBouncer Foreign Data Wrapper (pgbouncer_fdw).