You will get PostgreSQL tuned and a backup you can actually restore
Project details
Most Postgres slowness comes down to a handful of queries and a config that was never sized to the machine it runs on. I start by measuring: pg_stat_statements, EXPLAIN on the queries that actually hurt, and a look at what the server has to work with. Then I tune shared_buffers, work_mem, checkpoint and autovacuum settings to your real RAM and workload, add or fix indexes where the plans call for it, and hand you before-and-after timings so you can see what changed.
The backup half matters just as much. I set up automated dumps, and then a scheduled drill that restores them into a throwaway instance and compares row counts. If a restore ever fails, you hear about it that morning instead of during an outage. I run this same arrangement on my own seven-node fleet, where the restore drill has caught real breakage that the backup job reported as green.
You get the tuned config, the index changes, the backup and restore scripts, and a short written handoff covering how to run a restore yourself.
The backup half matters just as much. I set up automated dumps, and then a scheduled drill that restores them into a throwaway instance and compares row counts. If a restore ever fails, you hear about it that morning instead of during an outage. I run this same arrangement on my own seven-node fleet, where the restore drill has caught real breakage that the backup job reported as green.
You get the tuned config, the index changes, the backup and restore scripts, and a short written handoff covering how to run a restore yourself.
Database Type
PostgreSQLWhat's included
| Service Tiers |
Starter
$700
|
Standard
$1,500
|
Advanced
$3,200
|
|---|---|---|---|
| Delivery Time | 4 days | 7 days | 12 days |
Number of Revisions | 0 | 1 | 2 |
Source Code |
About Ian
Linux Infrastructure Engineer | Self-Hosted AI, PostgreSQL, Automation
Grand Rapids, United States - 8:13 am local time
WHAT I DO
Private AI on your own hardware. A language model running as a service on your machine, behind a standard API your existing tools can point at. Your documents and customer data never leave the building, and there is no per-token bill.
Linux servers that misbehave. I diagnose read-only first and send you the root cause in writing before I change anything. The fix comes with a rollback path and gets verified under load.
PostgreSQL. Slow-query audits, config tuned to the hardware you actually have, and backups proven by a scheduled restore that reads the data back and compares row counts.
Python automation. The recurring task somebody does by hand every week, turned into something scheduled and logged that tells you when it breaks.
HOW I WORK
I measure before I change anything, and I tell you what I found in plain language. You get the source code, the config, and a written runbook, so you are not dependent on me being reachable next quarter.
I would rather tell you something will not work than take a project that fails. If your problem is outside what I do well, I will say so.
Based in Michigan, US time zones, and I answer messages quickly.
Steps for completing your project
After purchasing the project, send requirements so Ian can start the project.
Delivery time starts when Ian receives requirements from you.
Ian works on your project following the steps below.
Revisions may occur after the delivery date.
Measure before touching anything
Read-only pass: pg_stat_statements, EXPLAIN on the expensive queries, current config against actual RAM and disk. You get the findings in writing first.
Tune, index, and verify
Config sized to your hardware, indexes the query plans call for, and before-and-after timings on every change so the improvement is visible, not asserted.