Yes, in that Postgres still uses oldest-to-newest tuple ordering, and its MVCC hasn’t changed, so you can still cause the issues listed. Careful monitoring and

Yes, in that Postgres still uses oldest-to-newest tuple ordering, and its MVCC hasn’t changed, so you can still cause the issues listed. Careful monitoring and tuning of parameters mentioned by the sibling comment to you can help mitigate this, though. Ultimately at scale, no, RDBMS shouldn’t be a queue. But most have a long way to go before they hit that point.