> problem is table design and write amplification. Every row insert triggers update into every index, so you get classic amplification problem.
Yes, this is understood. In particular for b-trees that require some refurnishing when growing. What's less understood is why Postgres hasn't solved this in a way similar to how InnoDB solves it behind the scenes.
