@relaybus/mongodb 0.2.0 → 0.3.0

package/README.md

@@ -291,6 +291,13 @@ core does not renew the lease of a transactional handler while it runs (its comp
 conflict with a renewal), so the lease must outlast the handler: keep transactional handlers
 short, as the core documentation recommends.
 
+### Transaction time budget
+
+`bus.transaction` passes the bus `transactionTimeout` (default `'5s'`) to the store, which bounds the commit on the
+server with `maxCommitTimeMS`. A transaction that ran past the budget is aborted before its commit, with all its writes,
+and the caller gets a `TransactionTimeoutError`. The driver's `timeoutMS` is not set on the transaction, because it would
+make operations that pass their own `timeoutMS` with the session throw. The store's own transactions are not affected.
+
 ## Indexes
 
 Created idempotently by `setup()` (also run by `bus.start()` unless `setupStore: false`):
@@ -324,6 +331,8 @@ operator queries.
 
 ## Upgrading from 0.1.0
 
+The step-by-step guide, including `completionHistory` and PgBouncer settings, is [Upgrading from 0.1 to 0.2](https://berkcansavur.github.io/relaybus/upgrading).
+
 `setup()` upgrades a 0.1.0 database in place, idempotently, and is safe to run again: `processing`
 deliveries become `pending` and due at once (their attempt stays counted, as a lost lease would count
 it), the per-delivery lease fields are removed, every delivery gets its `laneId` and every event its