Postgres UUIDv7 and per-back end monotonicity
How Postgres’ v7 UUIDs are made monotonic, and why that’s a great feature.
I'm Brandur. This site is where I publish words and photos. The section updated most often is atoms , short multimedia particles reminiscent of a Twitter feed. I update my now page monthly according to what I'm working on and thinking about. I publish a newsletter as often as I can.
Visit brandur.org → RSS feedOn Hacker News May 2017 – Aug 2026
Software Engineering 27Databases & Data 20Tech Industry & Business 7Systems & Performance 6Career & Management 4Web & Frontend 3
How Postgres’ v7 UUIDs are made monotonic, and why that’s a great feature.
Almost every notable managed Postgres provider bundles a connection pooler, giving us a strong hint that connection management is a product problem rather than a user problem.
Databases shed important RDMS features as they get big. Examining why this tends to be the case, and some ideas for preventing it.
It’s already been a great reading day for retrospectives on the last ten years / predictions for the next. Here’s to hoping that everyone had a good break (or at least a few days off), set or didn’t set resolutions, and is refreshed and ready for what comes next.
Building a robust background worker system that leverages transactional isolation to never work a job too early, and transactional durability to never let one drop.
Tracking improvements to Postgres partitioning since 2017. In just five years it’s gone from a non-feature to a very good one.