Excessive old rows have broken production systems for me. Performance degradations can break things!
Maybe you're a solo researcher doing data science.
I want my tools to be the best they can be. Always striving to be better. To push the limit and make things simply awesome.
I don't like defeatist attitudes or telling the user they are "holding it wrong".
Yes, of course we all want our tools to the best they can be, but that involves making tradeoffs in features because the maintainers don't have an infinite pool of time.
Postgres is a sufficiently advanced tool that if you're using it for any serious work you need to read the documentation for it. Ideally cover to cover, but at least skim the whole thing and pick out the important parts. The Postgres "Routine Database Maintenance Tasks" documentation [1] describes in great detail everything you need to do to keep your database working well.
Other than that, what is the complaint exactly? You do need to understand how your tools work if you want to use them correctly.
https://news.ycombinator.com/item?id=19119991
In that case they rejected a bugfix for something like 10 years, seemingly because of attitude issues.
Not that it forgives the fact the bug was reported 9 years ago and it just recently got fixed. I know personally I'd have messed it up.