An important part of performing a migration from Oracle to PostgreSQL is selecting the right tool for helping with the conversion between systems.
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).
Tested methods for upgrading PostgreSQL software from one major release to another with the least amount of headache.
Learn how the HPE SSD issues can impact your PostgreSQL data, and what strategies you can take to protect your data.
With the recent release of PostgreSQL 12, pgBackRest also received a number of updates and changes to take advantage of the latest features of Postgres.
A step-by-step guide for how to setup PostgreSQL change data capture with Debezium and Apache Kafka
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