I explain in another comment that I want jobs to be durable, so I can't just spin up a new thread. It's not the performance overhead that bothers me as much as

I explain in another comment that I want jobs to be durable, so I can't just spin up a new thread. It's not the performance overhead that bothers me as much as the session-sticky state and additional complexity in the database, my instinct is that it will cause outages in ways that take significant Postgres chops to diagnose and correct. That's just an instinct though, it could be far off base.