Queries that used to be fast are slow
Missing or unused indexes, out-of-date statistics, or a query plan that changed as the table grew.
Indexed and measured
Working with PostgreSQL?
Postgres rarely fails all at once. It gets a little slower every month until one morning the app can't connect. We find out what it is actually waiting on and fix that, with your data intact.
What it is
PostgreSQL, often just called Postgres, is an open-source relational database: the place an application keeps its records and answers questions about them. It is known for being strict about data correctness and for handling complicated queries well.
It runs on your own server or as a managed service from most cloud providers. It is free, but it is not hands-off: left on its default settings and never maintained, a busy Postgres database slows down in ways that are easy to miss until they are urgent.
The honest version
No technology is all upside. This is where PostgreSQL earns its place and where it tends to cause trouble.
Sound familiar?
The PostgreSQL problems that bring people to us, and what you have once each one is fixed.
Missing or unused indexes, out-of-date statistics, or a query plan that changed as the table grew.
Indexed and measured
Every app server opens its own connections until the limit is hit. Raising the limit only moves the crash.
Pooling in front of the database
Bloat from vacuum that can't keep up, often held back by a long-running or forgotten transaction.
Space reclaimed, vacuum tuned
Write-ahead log files piling up behind a broken replica or a failed archive job.
Back up, with alerts before it fills
An old major version that no longer gets security fixes, and nobody wants to be the one to touch it.
Upgraded with a rehearsed plan
A nightly dump that may or may not be complete, and no way to recover to a point in time.
Restores tested on a schedule
What we do
Call us for one slow query, or hand us the whole database.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Most often it is a small number of queries doing far more work than they need to, because an index is missing or the planner's statistics are stale. Default memory settings, table bloat and too many open connections are the other common causes.
The database has hit its connection limit. The lasting fix is usually a connection pooler such as PgBouncer and an app that reuses connections, not a higher limit.
Yes, when it is rehearsed. We run the upgrade against a copy of your data first, check the application against it, and only then schedule the real one.
Often, yes. A managed service takes backups, patching and failover off your plate. It does not tune your queries or design your indexes, and those are where most performance problems live.
Frequently, depending on what failed and what backups exist. The most important thing is not to delete or reinitialise anything before someone has looked at it.
Estimates are free. Describe the problem and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: