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:
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.
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.
Not being a big developer for myself, and only occasionally submitting patches here and there, I nevertheless have a vast amount of data available on the topic: the “PostgreSQL Person of the Week” interviews! There are a few questions in the interviews which relate to this topic:
The answer for me is very versatile, and covers quite a lot. Took me a moment to gather the facets, and likely I’m still missing some parts.
The PostgreSQL community for me is friends, databases, events, learning, speaking, teaching, writing, and much more.
Last week for “PGSQL Phriday” I posted the following task:
Describe how you do backups for your PostgreSQL databases.
And I added a bonus question: Is
pg_dump a backup tool?