Tuning · Migrations · Nashville, TN
PostgreSQL & MySQL tuning · zero-downtime migrations · Nashville, TN
A440Hz
A = 440 Hz is the note every guitar on Lower Broadway is checked against before the first set. Your database has a pitch too — usually its p95. We listen to slow PostgreSQL and MySQL the way a repairman listens for a buzzing fret, rewrite the queries and indexes causing it, and plan your move to a managed cloud database with the lights left on.
Fixed-scope engagements from $3,850 · invoiced, never metered
A missing index has a sound. It’s the replica fan spinning up at 2:14 a.m., the latency graph turning the colour of a bruise, a checkout button that hangs just long enough for someone to close the tab. We find that sound first — then we change the one thing making it, and nothing else.
The questions every CTO asks on the first call, answered in the sequence the engagement actually runs. If yours isn’t here, ask it out loud — the bench line is (917) 414-1843.
No. We ask for a read-only role on a replica — pg_read_all_stats on Postgres, PROCESS plus SELECT on performance_schema for MySQL. Nothing we run during the audit can write a row. Changes happen only after you’ve read and signed the change list.
Whatever is already humming in your logs: the top statements from pg_stat_statements or the MySQL slow log, EXPLAIN (ANALYZE, BUFFERS) output for the three queries your team groans about, a schema-only dump, and your current instance size. Five small files.
Ten business days for The Tuning. You get a written report ranking every finding by how loud it is — time saved per hour of real traffic — with the exact SQL for each fix, then a forty-minute walkthrough with your engineers.
We write it down, price it as its own line, and you decide. The fixed fee stays fixed; it never quietly swells between the kickoff and the invoice.
We plan around logical replication — native publications on Postgres, binlog replication on MySQL — and rehearse the cutover twice on a clone before production hears a thing. The switch itself is a connection-string flip in a window you choose, with a rollback that has actually been run.
It’s cut for exactly that: SaaS teams with no full-time DBA, whose database grew faster than anyone’s attention to it. Already have a DBA? We’re glad to be the second pair of ears in the room.
Four engagements, each with a start, an end and a single invoice. Pick the one that matches the noise you’re hearing — or call and describe it, and we’ll point.
$3,850 fixed · 10 business days
We read your pg_stat_statements like sheet music, find the queries playing flat, and hand back a ranked report — index changes, query rewrites, autovacuum and buffer settings — each with the SQL ready to paste.
EXPLAIN plans for every finding
$8,700 fixed · 3 weeks
We make the fixes ourselves: the twelve worst queries rewritten, indexes added with CREATE INDEX CONCURRENTLY or dropped, ORM call sites untangled — each change proven with timed plans on a production-sized clone.
From $14,600 4–6 weeks
A migration plan to RDS, Aurora, Cloud SQL or Azure Database — replication topology, cutover runbook, two full rehearsals, and a rollback that’s been run, not imagined.
Plan The Move$1,275 per quarter · after any engagement
We re-run the audit queries against your baseline and flag anything that has started to hum again, before it reaches the pager.
Add Second Listentotal_exec_time from pg_stat_statements — or the MySQL slow log with long_query_time = 1EXPLAIN (ANALYZE, BUFFERS) for the three queries your team sighs at in stand-uppg_dump --schema-only or mysqldump --no-data
Thackeray & Sons takes its name from a family habit: nobody turns a peg until they’ve heard the buzz. We kept the habit and swapped the instrument. Your slow log gets read by the same hands that write the final migration file.
Read the longer storyEach index we ship gets a COMMENT ON naming the query it serves — so in eighteen months nobody drops it during a cleanup and wakes the pager.
The audit never writes. Fixes go into a change list you read line by line before a single statement runs against your data.
No migration step leaves the bench without its reverse written beside it and tested on a clone the same afternoon.
One fixed fee per engagement, net-15, by ACH, check or card. No seats, no dashboard you didn’t ask for, no monthly meter ticking.
Invoiced net-15 after the report lands in your inbox — not a day before. ACH, check, Visa, Mastercard or Amex.
Ten business days, from read-only credentials to a ranked, written report you can hand straight to your team.
Bring the query your team groans about. We’ll open its plan with you live and tell you, honestly, whether an audit is worth it.
We’re based in Nashville, TN, in a front-room workshop on Cedarcrest Drive — radiator ticking through the winter, cicadas through the screen door in August. The tuning itself happens over a read-only connection; coffee, whiteboards and migration rehearsals happen here, by appointment.
Plot the route to Cedarcrest
The Tuning — a fixed-fee audit of your PostgreSQL or MySQL database: $3,850, ten business days, read-only access, and a ranked report your team can act on Monday morning.
Paste the query, describe the noise, or just tell us what the dashboard looked like last Tuesday at peak. We’ll write back with a time for a listening call.