river icon indicating copy to clipboard operation
river copied to clipboard

Fast and reliable background jobs in Go

Results 96 river issues
Sort by recently updated
recently updated
newest added

Hi, is it possible to make migrate do its migration inside a postgres schema and then connect to it with a client without actually spawning an entire new pgxpool(with `search_path`...

I haven't seen this in the api/docs, so please let me know if this is currently possible or not. **Description** Imagine there's a shopping mall with only one unloading point....

Hey 👋🏻 I'm not entirely sure why `jobCancelError` and `jobSnoozeError` are not exported as part of the public API, especially because `jobCancelError` also implements `errors.Is` and `errors.Unwrap`. What I'm trying...

When cutting new releases lately, I've noticed that pushing the "prepare vX.Y.Z" commit & PR for a new version causes the Go module cache the 404 on that new version...

bug

Hi, We are writing some stress tests to batch writes to an external data source, we have a worker that processes a job after x seconds and batches the data....

I'm very excited about this project, thank you and hats off! I have work function that calls: JobCompleteTx to atomicaly complete the job as well as perform other work on...

An infinitesimal change to add a missing pull request link for the change in #576.

I noticed [this failure](https://github.com/riverqueue/river/actions/runs/10930264275/job/30342796640). It ``` Run go test -p 1 -race ./... -timeout 2m go test -p 1 -race ./... -timeout [2](https://github.com/riverqueue/river/actions/runs/10930264275/job/30342796640#step:7:2)m shell: /usr/bin/bash -e {0} env: ADMIN_DATABASE_URL: ***localhost:54[3](https://github.com/riverqueue/river/actions/runs/10930264275/job/30342796640#step:7:3)2...

bug

A couple quick benchmarks for the two "insert many" variants to help vet whether or not we should keep the "fast" route. There is definitely a speed difference, with the...

I couldn't find an issue for this so I apologise if you're already aware of this. The "next" and "previous" links at the bottom of the documentation site are broken...

bug
documentation