Nightly `pg_dump` backup workflow + restore runbook

[Miracle656]

Background

Lens's aggregated price history lives in one managed Postgres. Losing it (provider limits, expiry, misconfig) means re-deriving from chain — slow. A nightly logical backup is the durability fallback for the mainnet deployment.

What to build

A free scheduled GitHub Actions workflow that pg_dumps to a dated artifact/release, plus a restore runbook. Covers both network DBs.

Key files

• .github/workflows/db-backup.yml — new
• docs/backup-restore.md — new

Suggested execution

git checkout -b ci/nightly-pg-dump

1. Scheduled workflow using a DATABASE_URL secret
2. pg_dump --format=custom → gzip → upload (retention ~14 days)
3. Runbook: pg_restore into a fresh Neon instance, swap DATABASE_URL
4. Handle separate testnet/mainnet DBs

Acceptance criteria

• Nightly job produces a downloadable dump
• Connection via secret (no creds committed)
• Restore verified once end-to-end
• Both network DBs covered

Drips Wave · Complexity: Easy · 100 points

---

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

[Bashibawa]

@Bashibawa has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi Maintainer, I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bashibawa to this issue.

[namdamdoi68-oss]

@namdamdoi68-oss has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Happy to set this up — a nightly pg_dump job plus a restore runbook. I'll check how you currently run the DB in prod/staging first so the backup uses the same credentials/rotation and doesn't stomp on anything.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @namdamdoi68-oss to this issue.

[drips-wave]

Congratulations, @namdamdoi68-oss! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @namdamdoi68-oss: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊