Vibhor Kumar describes a PostgreSQL extension:
That’s the promise of pg_background: execute SQL asynchronously in background worker processes inside PostgreSQL, so your client session can move on—while the work runs in its own transaction.
It’s a deceptively simple superpower:
- Kick off a long-running query (or maintenance) without holding the client connection open
- Run “autonomous transaction”-style side effects (commit/rollback independent of the caller)
- Monitor, wait, detach, or cancel explicitly
- Keep the operational model “Postgres-native” instead of adding another job system
Read on to learn more about it, including tips on how to use it and some examples of when you might want to use it.