# Backstage Catalog DB Performance

> Run and compare the Backstage catalog query performance battery against a safe database replica, capture PostgreSQL plans and buffers, detect regressions, and update the baseline. Use when changing catalog queries, indexes, schemas, or database performance behavior.

- Skill: `paulasilvatech/backstage-catalog-db-performance` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add paulasilvatech/backstage-catalog-db-performance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/paulasilvatech/backstage-catalog-db-performance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: Apache-2.0
- Author: paulasilvatech (https://skillmd.com/u/paulasilvatech)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/paulasilvatech/backstage-catalog-db-performance

---


<!-- Generated from harness/github-copilot/plugins/backstage-expert/skills/backstage-catalog-db-performance/SKILL.md by harness/claude-code/scripts/convert_from_copilot.py. Edit the source, not this file. -->

# Backstage catalog database performance

Use the pinned upstream procedure as detailed reference while protecting credentials and
production databases.

## When to invoke

- "Run the catalog query performance battery."
- "Compare catalog query plans to the baseline."
- "Check whether this catalog index change regressed performance."
- "Update the catalog database performance baseline."

## Procedure

1. Confirm Backstage core or close-fork mode and locate the catalog query battery and baseline.
2. Read [the pinned upstream procedure](references/upstream/catalog-db-performance.md).
3. Require a database replica or disposable test database. Do not run the battery against
   production.
4. Obtain connection details through environment configuration without writing or echoing them.
5. Establish catalog size and baseline comparability.
6. Run every documented scenario with its timeout, plan, timing, buffer, and anti-pattern capture.
7. Compare proportional timing and plan-shape changes to the previous baseline.
8. Update the baseline in its existing format only when the complete battery finished.
9. Report improvements, regressions, environment differences, and inconclusive scenarios.

## Output template

```markdown
## Catalog database performance result

**Database:** replica | disposable
**Baseline:** <path and date>

| Scenario | Plan change | Timing change | Buffers | Result |
| --- | --- | --- | --- | --- |

### Regressions
- <scenario, evidence, and recommendation>
```

## Quality gate

- [ ] The database is a replica or disposable test environment.
- [ ] Credentials were neither stored nor printed.
- [ ] Every scenario used the documented timeout and captured a plan.
- [ ] Catalog size differences are included in interpretation.
- [ ] The baseline changed only after a complete run.
- [ ] Regressions distinguish timing noise from plan-shape and index changes.