News for hackers. Stuff that matters.
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by u89012 on Tuesday April 11, 2023 @01:48PM (#35528578)
Would be nice if a little more detail were added in order to give anyone looking to do the same more heads-up to watch out for potential trouble spots. I take it the workers are polling to fetch the next job which requires a row lock which in turn requires a transaction yeah? How tight is this loop? What's the sleep time per thread/goroutine? At what point does Postgres go, sorry not doing that? Or is there an alternative to polling and if so, what? :)
Re:SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a... by adamckay on Tuesday April 11, 2023 @02:15PM (#35528967)
> Or is there an alternative to polling and if so, what? :)

LISTEN and NOTIFY are the common approaches to avoiding polling, but I've not used them myself (yet).

https://www.postgresql.org/docs/current/sql-listen.html

https://www.postgresql.org/docs/current/sql-notify.html