I was hoping this was going to talk about the phases of database growth/cost as in the development of PostgreSQL but rather it's about the phases as a user. St

I was hoping this was going to talk about the phases of database growth/cost as in the development of PostgreSQL but rather it's about the phases as a user. Still a good article where the first phase lines up with my experience exactly but I kind of lost the point of the second phase. To me phase 2 is 1) indexes, 2) partioning/sharding (and maybe introducing a Postgres addon or switching Postgres vendors to support this), and 3) rethinking what gets stored in Postgres in the first place or 4) setting up processes to migrate old data out of Postgres into s3 or something.