Postgresql

Guides· DeploySmith ·

pgBadger 13.3 on a VPS: PostgreSQL Log Analysis

Intermediate · 11 min read
PostgresqlPgbadgerLog-AnalysisVpsDatabaseSelf-HostingDevops

pgBadger 13.3 landed on November 3, 2026,[1] and it is one of those quiet maintenance releases that is worth paying attention to if you run PostgreSQL on your own VPS. Why now, specifically? PostgreSQL 19 general availability is planned for November 19, 2026,[4] which gives you a two-week window to do something most people skip before a major upgrade: look at what your current instance is actually doing. The logs PostgreSQL already writes are the highest-signal dataset on your box - no agents, no extra daemon, just the truth about slow queries, errors and disk spills. pgBadger turns that raw log stream into a single self-contained HTML report you can open in a browser. This guide covers the full loop on Debian or Ubuntu: what is new in 13.3, installing it, configuring PostgreSQL to log what pgBadger needs, running reports by hand and by cron, and reading the sections that matter. …

Read more →
Hosting· DeploySmith ·

Serverless Postgres vs VPS+PgBouncer

Intermediate · 9 min read
PostgresqlPgbouncerVpsManaged-DatabaseHosting

Managed Postgres is the default answer for most teams. But the pricing model of serverless databases (Neon, Supabase) and managed instances (Amazon RDS) is built around compute that is billed continuously, while a self-hosted PostgreSQL on a VPS is a fixed monthly cost that does not grow with your load. At some point the curves cross. For a steady, always-on workload, a single VPS running PostgreSQL plus PgBouncer is often dramatically cheaper than a managed database of equivalent size. This is that comparison: the economics, the latency story, and a decision table to help you pick. The version hook matters: PG14 is at end of life Before the cost comparison, a note on versions, because it directly affects a self-hosted setup. …

Read more →