With the bounds capped by a single writer. Unless you can shard the data and create a distributed database with manual sharding.
But yes. Postgres remains an amazing choice, especially with modern hardware, until you also have the money available to tackle said write throughput issue.
I think the point is that sharding won't really help that much since transactions will happen across all or most shards, and then you have certain accounts that will be more active than others.
Yes, sharding would kill performance under contention, which characterizes many OLTP workloads (e.g. top ten bestseller list on Black Friday, super stocks like NVIDIA, the big 4 banks on a switch, PhonePe/Google Pay on UPI etc)
But yes. Postgres remains an amazing choice, especially with modern hardware, until you also have the money available to tackle said write throughput issue.