So, when is message queuing just too much for easy async tasks?

I'm doing a project with some background tasks that don't need to happen right away, things like sending welcome emails or making reports. My initial idea was to use a message queue, maybe RabbitMQ or SQS. But after thinking about it, these tasks are pretty simple, and they don't really have tricky dependencies or need to be done in a specific order. So, at what point does setting up and taking care of a whole message queue system just make things more complicated than they need to be for these basic, occasional async jobs? Would something simpler, like just a basic producer-consumer setup using a database table, be enough or even better sometimes? It would definitely help avoid all the extra work that comes with a dedicated queue.