Another milestone for us at Icelandic Met Office 🎉
This week we launched a new site with #avalanche forecasts and conditions, including recent avalanches. A major update was required in the background, migrating to #Postgres and building the APIs and of course the website handled by our friends at Origo & Metall with maps from MapTiler
So... most gnome apps are failing to open on my debian sid daily driver. So... pgadmin4 won't open to remotely edit my company database. So... I have learned how to add a column to a table in my remote database using psql locally. Yup, I'm a hacker.
Ack, I dropped the wrong #postgres cluster last night and it nuked the databases for my #Forgejo and #Matrix Synapse instances. Of course the backups stopped working a year ago 🙃
I still have a 57GB base dir from the database, but no WALs or anything else. Don't think it's recoverable, though... I fear I will be picking up the pieces for a few weeks at least.
I love #SQLite. It just works. It is extremely fast, because it’s just a local file access. It is very operationally and mentally simple, and it is extremely stable and well-tested. However, over my years of using it, there are just some things that I miss from the world of #Postgres. So what happens if we just treat a local Postgres like SQLite? What does that mean? In this article, I’d like to expand on that idea.