Blake Gentry

Hmm, I think it's partly a bit overkill because I'm not sure the other modes would be needed, but primarily I think the default is wrong and will be a...

> Would it break river to run my own CleanStuckJobs task, putting deadlines per task and processing myself? To me adding this sort of "extension" to river would be preferred...

> the workersMap seems to be accessed in a thread-unsafe manner, which is okay if read only, but if i add a worker after Start() has been called, won't it...

> There's no way with `database/sql` to support listen/notify, so here we > introduce the idea of a poll only driver. River's client checks whether > a driver can support...

Thanks for reporting this @vito! I've fixed your issue (1) above as part of #79. This is something we used to have but broke during a refactor in the push...

The first part of this is resolved as per #79 and will be included in the upcoming release. It sounds like @brandur is eager to also see if we can...

If anybody out there is interested in giving this a try, `database/sql` functionality was merged in #351. We still haven't cut an official release with it (should come in v0.10.0)...

This was officially shipped last week: https://riverqueue.com/blog/database-sql Please let us know if you run into any issues with it!

FYI, there are some pretty significant changes to Sentry in v8: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md In particular, the mechanism for `startTransaction` used by `@envelop/sentry` has been removed.

@kyleconroy I think that would work perfectly well for what we would need, and it would be more flexible too (able to support fully qualified `my_db.my_schema.table_name` identifiers too). Given my...