Integrations / Any Postgres
Any Postgres
Neon, RDS, Fly, your own box — pg_cron anywhere.
Why connect it
pg_cron is the same everywhere. A connection string gives every non-Supabase Postgres user the full picture: every scheduled job, run history, failures, queue depth.
What you'll see
- Every pg_cron job with cadence, 7-day runs, failures, and the last error
- Queue depth and recent activity on the tables each loop touches
- Idle, failing, and never-run flags
What the credential can and cannot do
Where to get it: Your provider's connect page (Neon, RDS, Fly, Render Postgres…). Prefer a read-only role that can select from cron.job and cron.job_run_details.
It grants: Whatever that role can do. GitDoctor runs only reads.
It cannot: With a read-only role, nothing can be changed. Pausing a job is one line of SQL shown with its undo.
Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.