I'm far more hesitant to throw a more formal MQ in the mix though... mostly from experience in that a lot of mid level ("senior") developers don't really understand queues very well at all. Even if conceptually, using tables for queues is more complex.
That said, I will use PG for workflows similar to K/V, Document (JSONB) and other structures over reaching for say MongoDB, etc.
It's not that it's necessarily complex. But if you don't need it, don't use it. The business could use your time elsewhere
For a persistent store.. sure... but that's true for PostgreSQL as well, which has some pretty painful major version migrations by comparison to other options.
A better response to my comment could have been "just let it go" or something. ₍₍(˶>ᗜ<˶)⁾⁾