chore(deps): bump pg-boss from 10.4.2 to 12.30.0

[dependabot]

Bumps pg-boss from 10.4.2 to 12.30.0.

Release notes

Sourced from pg-boss's releases.

12.30.0

What's Changed

Schema version: 40 (a migration runs on upgrade — see Upgrading).

Fetch is now an ordered index walk instead of a sort, and maintenance reports when vacuum has stopped keeping up with the queues. Options priority and orderByCreatedOn are now deprecated.

Highlights

The fetch index matches the fetch

The fetch orders by priority desc, created_on, but the index led with start_after, so every poll read all eligible rows and sorted them. On a 500k-row job table that is a top-N heapsort over 5,257 buffers:

Limit (actual time=44.880..47.794 rows=1)
  Buffers: shared hit=5257
  ->  Sort  Sort Key: priority DESC, created_on
        Sort Method: top-N heapsort

The index now leads with the sort keys and keeps start_after as a trailing key column, so the same fetch is an ordered walk that stops at the first row:

Limit (actual time=0.079..0.080 rows=1)
  Buffers: shared hit=16
  ->  Index Scan using job_common_i11
        Index Cond: ((name = 'q') AND (start_after < now()))

47.8 ms → 0.11 ms, 5,257 buffers → 16. Cost is 27% more index (15 MB → 19 MB at 500k rows).

priority and orderByCreatedOn are deprecated

Both of these options were created to optimize perf, based on the previous index. As of this release, they are ignored and will be rejected in the next major. Jobs are always fetched in priority and creation order.

// no longer changes anything, and emits a DeprecationWarning once per option per instance
await boss.fetch('my-queue', { priority: false })

(node:1234) [PGBOSS_DEP_FETCH_SORT] DeprecationWarning: priority: false is deprecated and now ignored

Run with --trace-deprecation to find the call site, or --throw-deprecation to fail a build on it. It is a Node deprecation rather than a pg-boss warning event, which stays reserved for database and queue health.

If you set priority: false for throughput, remove it: it was measured roughly 180x slower than the default, since no index leads with created_on.

Vacuum health is monitored

A primary failure pattern of Postgres-hosted queues is a busy server that is unable to perform maintenance via autovacuum. Until now pg-boss reported a symptom via a warning about a queue's backlog, but the remedy for this wasn't clear. One easy solution to this warning is to increase workers, concurrency, or batch size. If the actual cause was related to a busy server, adding more polling workers or increasing busyness could instead make this issue worse, or at best not improve anything.

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for pg-boss since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)