Databases
Database Partition Cleanup: Drop Old Partitions With a Retention Plan
Database partition cleanup is a retention operation with sharp edges. Old partitions are attractive cleanup candidates because they have clear boundaries, but dropping the wrong one can break reports, restores, legal holds, or queries that rely on historical ranges.
The useful output is a partition retention plan with range inventory, consumer calendar, archive decision, maintenance window, and drop sequence. Keep the review concrete: Detach or archive the oldest partition before making the retention rule automatic, then make the next action visible to the team that owns the risk. That matters because the cleanup can still go wrong when dropping partitions before reporting windows close.
Key takeaways
- Treat each cleanup candidate as an owned system with dependencies, not anonymous clutter.
- Use the full retention period plus reporting, export, and audit schedules that read historical ranges before deciding that “quiet” means “unused.”
- Prefer reversible changes first when dropping partitions before reporting windows close is still plausible.
- Leave behind a partition retention plan with range inventory, consumer calendar, archive decision, maintenance window, and drop sequence so the next review starts with context.
- Measure the result as lower spend, lower risk, less operational drag, or clearer ownership.
Map Partition Ranges
Start with one partitioned table where partition ranges, retention policy, reporting jobs, backup coverage, foreign references, and maintenance windows can be reviewed together. The best cleanup scope is small enough that owners can answer quickly but wide enough to include the attachments that make removal risky.
| Field | Why it matters |
|---|---|
| Owner | Cleanup needs a person or team that can accept the decision |
| Current purpose | A short reason to keep the item, written in present tense |
| Last meaningful use | read/write activity, size, query plans, job dependencies, and retention rules |
| Dependency evidence | database metrics, query logs, application references, and reporting schedules |
| Risk if wrong | The outage, data loss, access failure, or rollback gap the review must avoid |
| Next action | Keep, reduce, archive, disable, remove, or investigate |
Do not make the inventory larger than the decision. A short list with owners and evidence beats a perfect spreadsheet that nobody is willing to act on.
Partition Evidence to Collect
The useful question is not “how old is it?” It is “what would break, become harder to recover, or lose accountability if this disappeared?” For database partition cleanup, collect enough evidence to answer that without relying on naming conventions.
| Check | What to look for | Cleanup signal |
|---|---|---|
| Range inventory | Partition names, lower and upper bounds, row counts, size, and oldest/newest records | A partition is older than the approved retention range |
| Consumer calendar | Reports, exports, audits, support queries, and backfills that scan historical ranges | No scheduled consumer needs the partition online |
| Backup and restore | Base backups, logical exports, archive tables, restore test, and encryption keys | A recoverable copy exists if policy requires one |
| Operational impact | Lock behavior, replication lag, maintenance window, and monitoring | The drop or detach can run without surprising production |
Use several signals together. Activity can miss monthly jobs and incident-only paths. Ownership can be stale. Cost can distract from security or recovery risk. The strongest case combines runtime data, dependency checks, owner review, and a rollback plan.
If the evidence conflicts, label the item “investigate” with a named owner and review date. That is still progress because the next review starts with a narrower question.
Example Evidence Check
List partition ranges and sizes before detaching or dropping old partitions.
SELECT schemaname, tablename, pg_size_pretty(pg_total_relation_size(format('%I.%I', schemaname, tablename))) AS size
FROM pg_tables
WHERE tablename LIKE 'events_%'
ORDER BY tablename;Treat the output as a candidate list. Do not pipe these checks into delete commands; add owner review, dependency checks, and a rollback path first.
Detach or Archive First
Use the least permanent move that proves the decision. In database partition cleanup, removal is only one possible outcome; reducing size, narrowing permission, shortening retention, archiving, or disabling a trigger may produce the same benefit with less risk.
- Detach or archive the oldest partition before making the retention rule automatic.
- Validate report windows and restore coverage before dropping historical ranges.
- Drop partitions in predictable batches with monitoring for locks, lag, and query errors.
Track the cleanup candidate with a simple priority score:
| Score | Good sign | Bad sign |
|---|---|---|
| Impact | Meaningful spend, risk, toil, noise, or confusion disappears | The item is cheap and low-risk but politically distracting |
| Confidence | Owner, purpose, and dependency path are understood | The team is guessing from age or name |
| Reversibility | Restore, recreate, re-enable, or rollback path exists | Deletion would be the first real test |
| Prevention | A rule can stop recurrence | The same pattern will return next month |
Start with high-impact, high-confidence, reversible candidates. Defer confusing items only if they get an owner and a date; otherwise “defer” becomes another word for keeping waste permanently.
Partitions You Should Not Rush
Some cleanup candidates are supposed to look quiet. Do not rush these cases:
- Quarter-end, audit, customer-export, and support workflows that scan old ranges.
- Partitions involved in replication, foreign references, or manual archive jobs.
- Tables where retention policy conflicts with customer deletion promises.
For these cases, use a longer observation window, explicit owner approval, and a staged reduction. The point is not to avoid cleanup; it is to avoid making the first proof of dependency an outage.
Run the Partition Review
Run database partition cleanup as a decision review, not an open-ended hygiene project.
- Pick the narrow scope and export the candidate list.
- Add owner, current purpose, last-use evidence, dependency checks, and risk if wrong.
- Remove obvious false positives, then ask owners to choose keep, reduce, archive, disable, remove, or investigate.
- Apply the least permanent useful change first.
- Watch the signals that would reveal a bad decision.
- Complete the final removal only after the review window closes.
- Save a partition retention plan with range inventory, consumer calendar, archive decision, maintenance window, and drop sequence.
For broader cleanup planning, use the cleanup library to pair this guide with related notes. If the cleanup has infrastructure impact, pair it with a visible owner, a rollback path, and a measurable business case. For infrastructure cleanup, the main cloud cost optimization checklist is a useful companion.
Automate Retention Boundaries
Prevention should change the creation path, not just the cleanup path. For database partition cleanup, the useful prevention fields are data owner, retention policy, recreate path, and review date. Make those fields part of normal creation and review.
- Define partition retention when the table is created.
- Schedule partition creation and removal as owned maintenance, not emergency cleanup.
- Keep archive location and restore test status beside the partition policy.
The recurring review should be short: sort by impact, pick the unclear items, assign owners, and close the loop on anything nobody claims. If the review keeps producing the same class of candidate, fix the creation path instead of celebrating repeated cleanup.
Example Decision Record
Use a compact record so the cleanup can be reviewed later without reconstructing the whole investigation.
| Field | Example entry for this cleanup |
|---|---|
| Candidate | Old partitions in partitioned databases |
| Why it looked stale | Low recent activity, unclear owner, or no current consumer after the first review |
| Evidence checked | Range inventory, Consumer calendar, and owner confirmation |
| First reversible move | Detach or archive the oldest partition before making the retention rule automatic |
| Watch signal | The metric, alert, job, route, query, or owner complaint that would show the cleanup was wrong |
| Final action | Keep, reduce, archive, disable, or remove after the full retention period plus reporting, export, and audit schedules that read historical ranges |
| Prevention rule | Define partition retention when the table is created |
This record is intentionally small. If the decision needs a long narrative, the candidate is probably not ready for removal yet. Keep investigating until the owner, evidence, reversible move, and prevention rule are clear.
FAQ
How often should teams do database partition cleanup?
Use the full retention period plus reporting, export, and audit schedules that read historical ranges for the first decision, then set a recurring cadence based on change rate. Fast-moving non-production systems may need monthly review; slower systems can be quarterly if every unclear item has an owner and a review date.
What is the safest first action?
The safest first action is usually ownership repair plus evidence collection. After that, detach or archive the oldest partition before making the retention rule automatic. That creates a visible test before permanent deletion.
What should not be removed quickly?
Do not rush anything connected to quarter-end, audit, customer-export, and support workflows that scan old ranges. Also slow down when the cleanup affects recovery, compliance, customer-specific behavior, rare schedules, or security response.
How do you make the decision useful later?
Write the decision as a small operational record: candidate, owner, evidence, chosen action, watch signals, rollback path, final date, and prevention rule. That format helps future engineers, search engines, and AI assistants understand the cleanup without guessing.