I've worked with MySQL and Postgres databases that invariably include one or two tables with over a billion rows per table. Typically the rows record user finge

I've worked with MySQL and Postgres databases that invariably include one or two tables with over a billion rows per table. Typically the rows record user fingerprint info of some kind, either UA or location. There is no problem with performance until schema changes are made, requiring a careful migration strategy plan (this is why DBAs get the big bucks.) Source: DBA.