4 ms·
You'll hit all sorts of other fun problems by vertically scaling. - Many concurrent connections to a single database which Postgres has traditionally not handl
by sa46 5y ago
You'll hit all sorts of other fun problems by vertically scaling.
- Many concurrent connections to a single database which Postgres has traditionally not handled well (though improved in recent versions).
- You're now on the hook for writing a database control plane.
- Backup and restore is much flakier since the data volume is so much larger. Lots of weird shit starts happening when you download tens of TB.
- In general, everything is a harder once you start nearing machine limits.
- jamesfinlayson 5y agoYes I thought Postgres didn't recommend more than 700 connections per server (or maybe it was 300) and that was only three or four years ago.