postgresql-operations

# PostgreSQL Operations Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. Use this parent skill as the active PostgreSQL operations entrypoint. Keep operational decisions tied to evidence: metrics, logs, query plans, lock graphs, replication state, backup history, and recovery objectives. <!-- dual-compat-start --> ## Use When - Troubleshooting slow queries, lock contention, bloat, vacuum pressure, replication lag, or connection exhaustion. - Designing backup, restore, HA, maintenance, monitoring, or capacity plans for PostgreSQL. - Reviewing production database configuration, operational runbooks, and incident evidence. ## Do Not Use When - The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow. - The request only needs a trivial answer and no reference module needs to be loaded. ## Required Inputs - Gather the concrete system, repository, environment, constraints, and deliverable before loading references. - Identify which absorbed reference file is needed; do not load every migrated reference by default. ## Workflow 1. Load `database-reliability` for SLOs, error budgets, incident posture, and recovery evidence. 2. Load the task-specific reference: - `references/postgresql-administration.md` for administration, backup, restore, roles, maintenance, and replication. - `references/postgresql-performance.md` for query tuning, indexing, EXPLAIN review, statistics, vacuum, and c...