You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we poll by default every 100ms for jobs unless a user change this on the config.
I think it'll be beneficial to also support Postgres LISTEN / NOTIFY (yes, the payload limit is 8KB) it would help with #17
I see PostgresNIO has support forLISTEN / NOTIFY, but it's not well documented. Maybe @fabianfett can help point us in the right direction?
What happens if the a job is added to the queue, but no job handler is running ie the LISTEN/NOTIFY is not running
These jobs won't be processed and marked as failed. The queue.cleanup func can be used to rerun these jobs should a job handler which can process these jobs become available.
Currently, we poll by default every 100ms for jobs unless a user change this on the config.
I think it'll be beneficial to also support Postgres LISTEN / NOTIFY (yes, the payload limit is 8KB) it would help with #17
I see PostgresNIO has support for
LISTEN / NOTIFY
, but it's not well documented. Maybe @fabianfett can help point us in the right direction?What do you think @adam-fowler @Joannis ?
The text was updated successfully, but these errors were encountered: