PostgreSQL Cost Optimization
Cut your PostgreSQL bill from inside the engine. OhChimp finds unused indexes, bloat, idle connections, and slow queries, then verifies real savings.
How does OhChimp find PostgreSQL savings the instance bill can't show?
OhChimp connects a read-only database user and runs probe queries against Postgres catalog and statistics views. That lets it see unused and duplicate indexes, table and index bloat, cache hit ratio, idle connections, slow queries, and temp-file spill, sources of waste a cloud billing dashboard never exposes.
Does OhChimp need write access or see my data?
No. OhChimp uses a read-only user, sets the session read-only with a 10-second statement timeout, and reads metadata and table or index statistics only. It never stores your application rows, secrets, or workload contents, and it warns you if the connecting role still has write privileges.
What PostgreSQL costs can OhChimp reduce?
Storage from unused, duplicate, and bloated indexes and dead-row table bloat. Compute from idle connections, slow queries doing sequential scans, lock contention, and temp-file spill that wants more work_mem. It also right-sizes memory from your cache hit ratio and flags oversized tables for partitioning and tiered archiving.
Who applies the changes, and can they be rolled back?
You do. Each fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and OhChimp applies the matching code and infrastructure changes together.
How are the savings verified, and what does it cost?
Savings are checked against your real bill. A plan is marked VERIFIED only after 7 or more days, a drop of at least 10%, and 3 consecutive positive checks. Otherwise it stays flagged "not implemented." Pricing is a flat monthly fee, OhChimp never takes a cut of savings, and paid plans carry a year-one ROI guarantee: a full refund of subscription fees if it does not pay for itself in the first 12 months.