Queueing jobs in Postgres from Node.js like a boss
MIT License
Bot releases are hidden (Show)
Published by timgit over 1 year ago
Full Changelog: https://github.com/timgit/pg-boss/compare/8.3.0...8.3.1
destroy
option for connection pool management during stop()
. PR #358 from @abelsoaresPublished by timgit about 2 years ago
db
option to fetch()
, send()
and insert()
to use an existing connection. The primary use case is for pg-boss to participate in a database transaction. PR from @klesgidisPublished by timgit over 2 years ago
work()
and onComplete()
. Previously, if a job was running that needed to create a new job, it would fail during a graceful stop.Published by timgit almost 3 years ago
Published by timgit almost 3 years ago
The primary theme of v7 is changing the semantics of the API to introduce a publish/subscribe feature that more closely aligns with other queue & messaging products that use a fan-out relationship between an event and subscription. Previously, pg-boss used publish()
for "create a new job" and subscribe()
for "poll a queue on an interval and execute a function".
publish()
renamed to send()
subscribe()
renamed to work()
subscribe()
will register a named event to a queuepublish()
will add a job to each subscribed queue per eventteamRefill
option added to work()
when using teamSize
to prevent longer-running jobs from delaying job processing in the worker.