Because postgres internally copies the entire row when any column is updated (this is cleaned up during a vacuum), having tables with many columns that update often is more IO and faster table growth.
Things like counter caches should be moved out to separate tables and queried with a join.
Because postgres internally copies the entire row when any column is updated (this is cleaned up during a vacuum), having tables with many columns that update often is more IO and faster table growth.
Things like counter caches should be moved out to separate tables and queried with a join.