I misunderstood what the heck the article was about at first. I hope this quirky analogy may help: "I am implementing a database for a bank. I open a transact

I misunderstood what the heck the article was about at first. I hope this quirky analogy may help: "I am implementing a database for a bank. I open a transaction in a special active_customers table when the customer first joins the bank, and commit the transaction when they close their account or die. In this way, I use postgres transactions to keep track of which customers are active customers. I am having problems with long-living customers forcing us to wait up to 120 years between autovacuums of the DB." Clearly, that's not going to be a good way to do things. Rossers comment (https://news.ycombinator.com/reply?id=14731214&goto=threads%3Fid%3Drosser%2314731214 https://news.ycombinator.com/reply?id=14731214&goto=threads%...) is very helpful.