Tim Jones

Yes, I will provide my thoughts. ;) I'm a bit concerned about this request because it blurs the lines between what a queue is and what a database is, so...

Are you imagining a solution that is also compatible with the bulk loading issue #310? As mentioned in that issue, debouncing is probably the biggest outlier. This is because it...

Hey, thanks! I agree with your suggestion, which is pretty similar to the expiration promise that is started along with jobs in the worker. I will look into an ideal...

This was intentional so I could more closely track completion times per job. However, after you opened this, I realize the larger the batch, the less helpful it becomes to...

Which singleton use case is the most important? If it were time-based throttling, for example, you could squash these pre-insert into time buckets via functions like date_trunc() in postgres if...

Have you tried `boss.insert([jobs])`? I realize it won't be able to offer all the features that `boss.send()` offers in regards to things like debouncing, but it may resolve at least...

To make sure I'm understanding, you're requesting a friendly error message when a migration is required but not allowed?

I would recommend you do option 4: keepuntil = startAfter + interval 'desired retention'. This is how the `plans.insertJob()` function works internally for deferred jobs: ```sql CASE WHEN right(keepUntilValue, 1)...

I agree that an option should be provided in `stop()` to control the closing of the pool

The short answer is no. Running a job from worker A doesn't prevent job fetching by worker B. There are a few options you can configure during send(), such as...