Performance

PostgreSQL 🐘 is a robust database, but its MVCC (Multi-Version Concurrency Control) design can sometimes lead to a subtle issue: table and index bloat. If left unchecked, bloat wastes storage, increases I/O, and can slow queries down. In this post, I’ll walk through: What bloat is and why it happens Different ways to measure it How to keep an eye on it without killing your database A few habits to reduce or fix it What is bloat? 🧹 Table bloat: Every update creates a new row version, and the old one becomes dead. Those dead tuples sit there until vacuum cleans them. Index bloat: Even when dead tuples are gone from the table, their index entries may stick around until an index vacuum or reindex. Why care? ...

🚀 The Pagination Pitfall: A React + Spring Boot Cautionary Tale The Setup: “It’ll Be Fine…” A few years ago, I was working on a dashboard application with a React frontend and a Spring Boot backend. The task seemed simple: display a list of users with pagination. One of the newer devs suggested: “Let’s just fetch everything once and paginate on the client side — it’ll be faster for the user.” ...

For years, I’ve been using Jekyll to power my blog at ozkanpakdil.github.io. It has served me well in production, but setting it up on Windows for local testing has always been a bit of a headache. Even with WSL, the process is sluggish, making experimentation and quick iterations more cumbersome than I’d like. Recently, I started thinking about creating a PostgreSQL benchmark center website, and given my past challenges with Jekyll, I decided to explore other options. That’s when I discovered Hugo, a static site generator built with Go. I went ahead and created the site under GitHub Pages at pgbench.github.io, and the difference in speed was immediately noticeable. ...