Showing Post From PostgreSQL
Background jobs on PostgreSQL in 2026: revisit River, Graphile Worker and Oban before you add Redis just for a job queue
Most web applications need background jobs. Send an SMS after a payment, build a PDF, call a slow partner API, recalculate a report at night.
Read morePostgreSQL backups in 2026: revisit pgBackRest, WAL-G and Barman before you trust another restore
Picture a company in Bhopal that runs a cab and auto-rickshaw dispatch and fare platform for Bhopal, Indore, Ujjain and Dewas (an invented example, not a real client).
Read morePostgreSQL high availability: revisit Patroni and CloudNativePG before your next failover
Picture a lending company in Bengaluru (an invented example, not a real client). Its loan ledger runs on PostgreSQL 16 across three VMs, managed by Patroni with a three-node etcd cluster and HAProxy in front.
Read morePgBouncer and its alternatives: revisit your PostgreSQL connection pooler
A team runs about forty services on Kubernetes against one PostgreSQL primary. During a sale, the autoscaler adds pods, each opens its own pool of ten connections, and PostgreSQL starts refusing logins with “remaining connection slots are reserved”.
Read morePostgreSQL asynchronous I/O: revisit your settings before you upgrade
A team upgrades its reporting database from PostgreSQL 16 to 18 over a weekend. On Monday the nightly scans finish a little faster, and nobody knows why, because nobody changed a setting.
Read more