Illuminated Computing

With UPDATE/DELETE FOR PORTION OF looking like it will land in Postgres 19, I’ve been thinking about next steps.

I seem to have an unusual way of running Claude Code, but I find it a good trade-off between convenience and security.

I got a GeForce RTX 5070 Ti GPU for Christmas.

I had to fix some shift/reduce conflicts in the Postgres bison grammar recently.

Logical decoding is different from logical replication.

Both logical decoding and logical replication use a table’s REPLICA IDENTITY.

Way back in Februrary Peter Eisentraut asked me if I’d tested the performance of my patch to add temporal foreign keys to Postgres.

Last Thursday I gave a talk at PDXPUG about using Benchbase to compare the performance of temporal foreign keys.

Benchbase is a framework from Carnegie Mellon for benchmarking databases.

One silver lining of temporal primary & foreign keys getting reverted is I got to meet Hettie Dombrovskaya and Boris Novikov.

Saturday I debugged the sprinklers.

My work adding temporal primary keys and foreign keys to Postgres was reverted from v17.

Here on illuminatedcomputing.com I’ve got a bunch of sites served by nginx, but I’d like to run a little k3s cluster as well.

The kids and I love to play games on the weekend.

UPDATE: My temporal patches were reverted from v17.

In Postgres development it’s normal for patch attempts to require many revisions and last a long time.

When it comes to sending email in Rails, I’ve wondered for years about the gap between this: class UserMailer < ApplicationMailer def welcome(user) @user = user mail(to: user.email) end end and this: class User def send_welcome_notification

Ubuntu has a very nice way of organizing multiple versions of Postgres.

Rails has lots of methods to see what attributes have changed on your model.

Introduction This blog post is a survey of SQL:2011 Temporal features from MariaDB, IBM DB2, Oracle, and MS SQL Server.