Introvert, history enthusiast, and occasional amateur photographer. Mostly I code, but sometimes I feel like writing. Spent 5 years as a digital nomad, fi...
I've been looking for a way to start exploring the PostgreSQL source code. The code is extremely well linked, with every commit linking to a message or a thread, and the message archives linking to patches. However, none of those links can be scripted or queried, and the archives are huge. So I'm introducing pgLantern , which is my solution in the form of a free API connected to a pipeline that…
When browsing the default Postgres extensions (a perfectly normal activity), I discovered pg_trgm . After a bit more reading , I'm convinced this simple database extension should be an essential part of any database engineer's toolkit. From the documentation: The pg_trgm module provides functions and operators for determining the similarity of alphanumeric text based on trigram matching, as well…
I used to agonize over naming my projects. First there's sweating over the repository name, then the repository name eventually leaks into the top-level module name. And the database. And the package. Eventually I figured it out: Dumb. Project. Names. Using machine vision to plot deforestation? Demeter. Visualizing the political machinations of the French Revolution? Guillotine. A system…