Bouncing of Ideas

This is a verbatim conversation I had with an older LLaMa 3 model hosted on my PC via Ollama a few days ago. It started because I wanted a translation for the name of an X account named gatos fazendo gatices, and it just kind of spiraled from there. The topic eventually touched on how AI could be improved, the effects on society, and the nature of cognition itself. It’s clear the LLM has a tendency to restate the question as part of the answer, or at least mine was.

PG Phriday: My Postgres is Rusty

Postgres and Rust go together like peanut butter and chocolate, or ice-cream and root beer, or Batman and Robin, or mice and cheese, or sand on a beach, or crabs and elephants! Err, maybe scratch that last one.

Hmmmmm…

Hmmmmm…

Well regardless, there’s a whole lot of Rust going on in the Postgres world these days, especially thanks to contributions from the PGRX project. As a relative novice to Rust, I figured it was time to see what all the fuss was about and tentatively dip a foot into those turbulent and unforgiving waters.

Tripping Out

Last week was a very odd conjunction of coincidence I’m still trying to understand. The aftermath of which left a reverberating melancholy and nostalgia, difficult to dispel, and all too tempting to embrace. It was one of those times where I question the entropy of the universe itself, as pure serendipity would be an impossible convergence. And yet.. An Expert Opinion I drove to Chicago on Tuesday to present a talk on the pg_timeseries extension to the Chicago Postgres User Group.

Fourth of Denied

Though there is unpacking yet to do, we’re settling in rather well. It’s just a matter of time now, as all things usually become. I no longer become hopelessly lost driving around without navigation. Jen is making progress on her office. Fun times all around! What’s important is the core of the house is essentially done, and we can work from there. Nice, eh? The sideboard / TV-stand is now, as is the cabinet bookcase.

PG Phriday: Taking Postgres for GRANTed

Not every database-backed application needs to be locked down like Fort Knox. Sometimes there are even roles that leverage blanket access to large swathes of available data, if not every table, simply for auditing or monitoring purposes. Normally this would require quite a bit of preparation or ongoing privilege management, but Postgres came up with a unique solution starting with version 14: predefined roles. This topic comes up relatively frequently in Postgres chats like Discord, Slack, and IRC.