Insights & how-tos

Blog

Practical, hands-on guides from our database, cloud and software teams — the same kind of write-ups we lean on internally, shared for anyone running these platforms themselves.

Database

PostgreSQL pg_wal Growing Too Large: How to Check Replication and Safely Clean Up WAL Files

· 16 min read

Is your PostgreSQL pg_wal directory consuming unexpectedly large amounts of disk space while your standby server contains only recent WAL files? This guide explains how to verify streaming replication, identify what is retaining WAL, troubleshoot replication slots and WAL archiving, and safely allow PostgreSQL to reclaim disk space without manually deleting critical WAL files.

Database

Troubleshooting Oracle TEMP Tablespace When the Filesystem Is 100% Full

· 21 min read

When the filesystem hosting Oracle TEMP tempfiles reaches 100%, simply checking the TEMP tablespace's reported used space is not enough. This guide explains how to determine the physical tempfile size, reusable TEMP space, active TEMP consumers, SQL responsible for TEMP growth, historical usage, and safe remediation options for Oracle 10g and Oracle 19c.

Database

How to Set Up and Monitor SQL Server Log Shipping

· 16 min read

SQL Server log shipping is a proven disaster recovery solution that maintains one or more secondary copies of a production database by continuously backing up, copying and restoring transaction-log backups. It is available in SQL Server 2019 and other supported SQL Server versions. It is commonly used when organisations need a cost-effective warm standby database without the clustering requirements and licensing complexity associated with some high-availability technologies.

Database

How to Reduce Excessive PostgreSQL Log File Growth in Production Environments

· 10 min read

PostgreSQL logging is essential for troubleshooting, performance monitoring, auditing, and operational support. However, incorrectly configured logging can quickly consume large amounts of disk space and create unnecessary operational risk. In a recent production scenario, a PostgreSQL 15 environment was generating more than 20 GB of logs per day, with approximately 150 GB of disk space consumed in less than a week. This article explains how to identify the root cause of excessive PostgreSQL logging, safely reduce log volume, improve rotation and retention, and understand the impact of these changes in a streaming replication environment.

Have a topic you'd like us to cover?

Tell us what you're wrestling with and we may turn it into the next guide.

Get in Touch