Skip to content
TopicTracker
From HackerNewsView original
TranslationTranslation

Show HN: Pgblame – which Vercel deploy slowed your Postgres?

Pgblame is a new tool that helps identify which Vercel deployment caused a slowdown in your PostgreSQL database by correlating deploy timestamps with database performance metrics.

Background

- **pgblame** is a new open-source tool that helps developers identify which specific deployment of their application caused a PostgreSQL database to slow down or regress in performance. - It works by correlating query performance metrics (e.g., from pg_stat_statements) with deployment timestamps from platforms like Vercel, GitHub Actions, or other CI/CD systems. - Vercel is a popular cloud platform for frontend and serverless functions; many teams deploy frequently (sometimes many times a day), and a single bad deploy can introduce a slow query that drags down the whole database. - Without a tool like pgblame, tracing a database slowdown back to a particular code change or deploy requires manually cross-referencing logs, deploy times, and query stats — a tedious and error-prone process. - This matters because as apps grow, database performance is often the bottleneck; pgblame aims to close the loop between "the DB is slow" and "that deploy at 2:14 PM did it."