Problems with large tables in Postgres
Tell me to stop when I name the largest table in your database: logs, ledger, notifications, feed, events, chonk ... admit it, I got it, right? Product success leads to lots of data, lots of data leads to big tables, but big tables lead to predictable problems. A table can be large (many rows), wide (many columns), or "fat" (oversized values). Any of these can cause you problems. How a large table can cause an outage First, let me tell you a story. A customer had two tables, A and B. Table B is
