Adopt LISTEN/NOTIFY strategies for PostgreSQL

[xjunior]

Hi, and thanks for all the work on Solid Queue!

We’re currently evaluating Solid Queue as a replacement for our existing backend job system and had a question about future Postgres support.

What are the chances of Solid Queue adding support for Postgres LISTEN/NOTIFY as a delivery mechanism or configuration option when running on Postgres? We’re particularly interested in understanding whether this is on the roadmap (or considered out of scope) so we can better plan our long‑term adoption strategy.

To be clear, this isn’t a blocking requirement for us right now, but it’s an important factor in how we think about the future of our queueing infrastructure with Solid Queue.

Thanks again for your time and for maintaining this project.

[rosa]

Hi @xjunior, and thanks so much for your kind words 🙏🏻

At the moment, it's very unlikely we'll add that, to be honest. It's too specific for PostgreSQL. This aims to be quite generic so that it works mostly in the same way with the 3 RDBMS supported by Rails officially. We have some specific optimisations for each of them, but the general operation is exactly the same. That would be too much of a divergence. I'd say the chances are close to zero.

For a PostgreSQL-specific queue backend, I recommend GoodJob, it's really great! It has a ton of features, and it's quite mature.