Results 134 comments of Tim Jones

Please try this again in 9.0.2 and see if it's resolved

PRs are always welcome. I think it should be opt-in via as a new option on stop(). Thanks!

Hold off on the PR. v10 will include this

Apologies for the long turn around time on this release. There's a few problems I'm still looking at.

Yes, I think you should update to latest and re-validate

A couple things 1. You should add an error event listener: boss.on('error', ...) 2. You should only use send() + work() and not publish() + subscribe() since these were changed...

I treat pg-boss in my API like a connection pool. It's a long-lived object that is created by a service that stays running for the entire uptime of the application

If this would be resolved by simply passing any additional configuration through to node-pg, that seems like a good solution. Did you already try using `keepAlive`?

I don't run pg in RDS so any testing and feedback you can do would be appreciated.