Review PostgreSQL Patches

Use a local SQLite database to retain review knowledge across sessions. Treat the database as an index of claims and provenance, not as a replacement for the source thread or patch.

Set PG_HACKER_MEMORY_DB to select a database. Otherwise use ~/.local/share/postgres-hacker-skills/review-memory.sqlite3.

Prepare context

Use search-pg-hackers to retrieve the thread and persistent patch store. Save its thread JSON, then ingest both artifacts:

python3 scripts/review_memory.py ingest \
  --thread-json thread.json \
  --patch-manifest thread-work/manifest.json

Before reviewing, extract changed file paths, important symbols, subsystem names, and topics. Recall related findings: