Good overview on how the databases landscape evolved the past year.

Interesting explanation of a research paper exploring the possibility of a faster SQLite by focusing on async I/O.

This is a nice view into how a query planner roughly works and a nice algorithm which can be used internally to properly estimate the number of distinct values in a column.

If you wonder how the protocol is designed and how the actual implementation works, this is a nice introduction. Clearly it's helped by the size of that program which is fairly small.

A good reminder that I should probably evaluate DuckDB for some of my tooling.

I definitely like the approach of having vectorisation in the RDBMS directly. This is one less moving part, less complexity at the application level to synchronize everything together. In this case it's a Postgres extension.

Interesting, there's now an official tool to replicate sqlite databases. It's still early days, we'll see which features it'll get.

Another nice list of defaults for SQLite. Some of them I didn't have on my radar.

Since everything has design choices which imply trade offs. Here is the main issue with PostgreSQL right now. Hopefully it'll get modernized at some point.

I'm not sure I'm sold on this one. Interesting food for thought but I'll have to mull it over for a while I think. I'm concerned about the performance implications of querying like this.

Wish to use SQLite in production? You better have a good backup strategy. This article explains the main available options.

Lots of things to keep in mind when dealing with databases. This is a nice list of "must know" for developers, false assumptions are widespread (and I fall in some of those traps myself from time to time).

A weird detour via baseball obscure rules to justify why we should pay attention to the "Highlander problem". This should be kept in mind especially for designing databases.

Looks like an interesting way to improve SQL. This feels like a nice extension, it's much better than throwing out the baby with the bathwater.

Need to duplicate data in Postgres? Several options are on the table.

Looks like an interesting tool for creating anonymized pre-production environments.

Looks like a neat extension which can come in handy.

Definitely not as simple as it sounds. The devil is once again in the details.

Interesting experiment showing that BLOBs in a database can be a good alternative to individual files on a filesystem in some contexts.

Some improvements coming in SQLite transactions. Here are some early tests.