4 ms·
MySQL doesn't need the auto-vacuumer to be tuned, as it doesn't have one. I've had Postgres servers crash due to excessive stale rows...
by etaioinshrdlu 5y ago
MySQL doesn't need the auto-vacuumer to be tuned, as it doesn't have one. I've had Postgres servers crash due to excessive stale rows...
- yarcob 5y agoPostgreSQL is vulnerable to certain workloads. For example, if you keep appending something to a text column, you'll use up a lot of disc space since PG will copy the row each time and keep deleted copies around until autovacuum comes along. Of course, if you are doing this then you are using your database wrong -- but it's still something that's easy to run into.
- jkatz05 5y agoPostgreSQL 14 made improvements to this area around indexing: https://www.postgresql.org/docs/14/btree-implementation.html#BTREE-DELETION https://www.postgresql.org/docs/14/btree-implementation.html...
- mattashii 5y agoYes, but that doesn't cover the problem of bloat in the TOAST tables due to excessive churn of large attributes that was mentioned in the parent post.