We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After migrating from single messages table, queue service can now use database more efficiently, but there's still room for improvement.
Queue service still uses polling to fetch new tasks for queues, and this can be improved with using notify/listen in postgres
notify
listen
This is the last item remaining from #2940 (comment) migration
The text was updated successfully, but these errors were encountered:
I suspect this will remove a lot of load from the DB servers! 🚀
Sorry, something went wrong.
No branches or pull requests
After migrating from single messages table, queue service can now use database more efficiently, but there's still room for improvement.
Queue service still uses polling to fetch new tasks for queues, and this can be improved with using
notify
/listen
in postgresThis is the last item remaining from #2940 (comment) migration
The text was updated successfully, but these errors were encountered: