Tag Archives: PostgreSQL comparison
There was a time when PostgreSQL’s own developers were far more open about the real cost of their MVCC design. Back in the 8.1 era, the documentation spelled out the resource drain, the vacuum overhead, and the “cold comfort” of wraparound risk in plain language. I first read that line in 2003, and it stuck with me for more than twenty years. I could not imagine any serious operations team wanting a database that required a separate background process to clean up transactions long after they had completed. PostgreSQL has absolutely improved vacuuming — autovacuum, visibility maps, HOT updates, parallel vacuum, better defaults, better alerts.
…
Continue reading “The Real Operational Cost of Vacuuming in PostgreSQL”
Mirror, mirror on the wall — what do you measure when you measure us all?
Is it skill, or is it voice?
Is it code, or is it conversation?
DB-Engines is not a looking glass of perfection, but a mirror of perception — reflecting the chorus of those who search, speak, teach, compare, and build. And like every enchanted mirror, it shows not only what is, but what the world believes it sees.
MariaDB today stands firmly among the world’s top relational databases.
Not by inheritance, and not by illusion, but by the millions who use it, trust it, and shape it.
…
Continue reading “Mirror, Mirror on DB-Engines: The MariaDB Story”