Can't believe it's 5 years since my first pull request. Now sharing RegreSQL as my own fork.

boringsql.com/posts/regres...

“Early in our company’s life, we built everything around modern data frameworks — until we realized the simplest, most reliable tool had been in front of us all along”

blog.sturdystatistics.com/posts/sql/

Range types are one of PostgreSQL’s most underutilized features — let’s change that boringsql.com/posts/beyond...

#postgresql

Back after the summer break with a new article on PostgreSQL security: performing common maintenance tasks without distributing SUPERUSER privileges.

boringsql.com/posts/postgr...

Attending ViennaDB meet up

Time to Better Know the Time in PostgreSQL Article URL: https://notso.boringsql.com/posts/know-th...

https://notso.boringsql.com/posts/know-the-time-in-postgresql/

Event Attributes

Back with "VIEW inlining in PostgreSQL" notso.boringsql.com/posts/view-i...

A good way to end 2024 - migrating personal servers to FreeBSD

Meet me and other PostgreSQL enthusiasts in London (UK) next week www.meetup.com/london-postg...

Impostor syndrome always hits me hard when something gets this much exposure 🙈

You can probably guess where this leads. Since transactions are already a pain for developers, imagine the chaos when issues hits the production. Locks and a growing queue of waiting statements are inevitable… Fun starts in 3, 2, 1.

Preparing a draft for the next article, which touches on transaction isolation (not the main topic though). This means the text needs to be super clear and include plenty of examples. Transactions are the number one source of pain for the majority of developers (unfortunately).

ORM are evil. SQL is meant to be handcrafted.

Not really doing anything for optimising SEO and stuff like that, but it's surprising to see ChatGPT as referrer for boringSQL more and more 🤔