The topic for this month’s PGSQL Phriday blogging challenge is: pg_stat_statement. And Michael Christofides gave me a perfect opener in his invitation.
For anyone who doesn’t know, I’m running a weekly interview series with people from the PostgreSQL community. It’s called “PostgreSQL Person of the Week”. One of the questions in the default set I give everyone is:
This month’s #PGSQLPhriday is hosted by Lætita Avrot, and she asks about triggers.
History time. Shortly after I started using PostgreSQL, I had a need to track changes in tables. Back then - this was the early version 7.x days - there was no such option available. I set out to write a tool for it. The logical choice to do that was to pick triggers to implement this. Today the world is different, PostgreSQL gained replication, and along with this, one can hook tools into the replication and stream all the changes. Back then there was no replication.
From time to time our laptops receive firmware updates, by using the Linux Vendor Firmware Service (short: fwupd). This worked fine for a long time, until it didn’t. One day I was facing the following error message:
I’m moving files from one QNAP system to another, and I’m using rsync for this. It’s preinstalled on a QNAP system. So far, so good.
To sync entire shared volumes, I want to exclude the @Recently-Snapshot and @Recycle entries - I don’t want to sync the trash bin and I also don’t want to sync entire snapshots.
The usual approach when using rsync is to just use the --exclude option.
For this month’s #PGSQLPhriday, Grant Fritchey asks: What is the one thing you wish you knew while you learn PostgreSQL.
With people moving away from Twitter, mostly to Mastodon, discovering the new accounts became a problem.
For people in the PostgreSQL community I created a website which lists different social media accounts. This website is part of the “PostgreSQL Person of the Week” interview project, however the data source is dynamic, and stored in a different repository. This allows me to keep the repository for the website private, but publish the data for the social media links - this data is public anyway. The interview repository is private, because who wants to see upcoming interviews anyway? ;-)
Someone at FOSDEM 2023 asked the question: “What happens when PostgreSQL rolls over the version number to 95? Will this cause problems like back then in Windows?”
What does that even mean? When Microsoft released the version after Windows 98, they opted for naming it Windows 10, not Windows 9. Because apparently a lot of code out there checks if the string starts with “Windows 9” and then assumes that the OS is one of the very old ones. This might not be the only such problem, as another blog article by Microsoft shows. Apparently they used “3.95” for the Windows 95 internal version, because lazy programmers.
Ryan Lambert asks in this month’s PGSQL Phriday:
Ran into a curios problem while updating the GitHub Actions Workflow for a project:
If you use GitHub Actions to run Workflows and tests, you might have spotted this warning recently: