Can you be more specific about the issues you have run into that make you advise GoodJob over SolidQueue? I am (and have been for a while, not in a hurry) cons

Can you be more specific about the issues you have run into that make you advise GoodJob over SolidQueue? I am (and have been for a while, not in a hurry) considering them each as a move off resque. The main blocker for me with GoodJob is that it uses certain pg-specific features in a way that makes it incompatible with transaction-mode in pgbounder -- that is, it requires persistent sessions. Which is annoying, and is done to get some upper-end performance improvements that I don't think matter for my or most scales. Otherwise, I much prefer GoodJob's development model, trust the maintainer's judgement more, find the code more readable, etc. -- but that's a big But for me.