A bounded investigation of one production PostgreSQL cluster and its dominant workload—using read-only evidence, human-reviewed findings and a measurable validation plan.
Founding price $450 for the first three suitable engagements · Report within 5 business days of receiving agreed evidence · No production access required
p95/p99 grows, database CPU climbs, or a few statements dominate total workload time.
A release, version change, data growth or statistics shift changed plan behavior.
Blocking, lock queues, long transactions, connection storms or pool saturation appear under load.
Report delivered within 5 business days of receiving the agreed evidence. No 24×7 incident-response promise and no production write access.
Define the production symptom, business impact and evidence boundary.
Client-run read-only evidence: workload, plans, locks, indexes and relevant settings.
Correlate signals and distinguish the symptom from likely root cause.
Rank findings by impact, confidence, risk and implementation effort.
Define rollback and before/after checks so the team knows whether the change worked.
Most of this comes from one read-only collector script.
One PostgreSQL cluster and its dominant production workload. The fit review identifies the symptom, evidence available and decision your team needs to make. Additional clusters or unrelated workloads need a separate scope.
No. Your team runs agreed read-only collection and reviews the evidence before sharing it. Credentials and production dumps should stay in your environment.
The report separates supported findings from hypotheses, states confidence and missing evidence, and recommends the next useful test. A guaranteed performance gain is not part of the offer.
Your engineering team owns production changes. If implementation help is useful, a bounded remediation sprint can be scoped separately after the findings are reviewed.
Your team executes changes. I investigate, prioritize and define validation.
This is scheduled specialist work, not a substitute for an on-call DBA/SRE incident function.
Performance improvement depends on workload, implementation and system constraints.
Candidate analysis may use automation, but client-facing findings remain human-reviewed and evidence-linked.
Used to build independent proof and refine the delivery system.
Request fit reviewFinal scope depends on cluster/workload complexity and evidence available.
See pricing modelStart with the problem and the evidence you already have. You will get a direct answer on whether a scoped investigation is the right next step.
Prefer to talk first? Book a 20-minute triage call.