Maybe, but I think MariaDB beats all of them at that.
Also, though, horizontal scaling is a lot less important now than it was 20 or 30 years ago. https://www.servethehome.com/2025-server-starting-point-inte... says AMD has 192 cores per socket, and you can get two-socket motherboards, so 384 cores total. And you can stick 12 128GiB DDR5-6000 DIMMs in it, so 1.5 tebibytes of RAM, and a single SSD is 30 terabytes, and SSDs can commit a transaction group durably in typically 0.1 milliseconds. And those 384 cores (EPYC 9005, so Zen 5c, https://www.servethehome.com/amd-epyc-9005-turin-turns-trans...) are 2.25GHz and typically about 2.2 instructions per clock (https://chipsandcheese.com/p/zen-5-variants-and-more-clock-f...), and they support AVX512.
As one rough estimate, 2.25GHz with AVX512 (at 1 IPC) means you can do 36 billion column-oriented 32-bit integer operations per core per second, which with 384 cores means 13 trillion 32-bit integer operations per core per second. On one server. So if you have a query that needs to do a linear scan of a column in a 13-million-row table, the query might take 300μs, but you should be able to do a million such queries per second. But normally you index your tables so that most queries don't need to do such inefficient things, so you should be able to handle many more queries per second than that!
(Each socket has 12 DDR5 channels, totaling 576 gigabytes per second to DRAM per socket or 1.13 terabytes per second across the two of them, so you'll get worse performance if you're out of cache. And apparently you can use 512GiB DIMMs and get 6 tebibytes of RAM!)
So, if you need more than one server for your database, it's probably because it's tens or hundreds of terabytes, or because you're handling tens of millions of queries per second, or because your database software is designed for spinning rust. Spinning rust is still the best way to store large databases, but now the cutoff for "large" is approaching the petabyte scale.
I think the space of databases that are under ten terabytes and under ten million queries per second is large enough to cover almost everything that most people think of when they think of "databases".