mindly.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mindly.Social is an English speaking, friendly Mastodon instance created for people who want to use their brains and their hearts to make social networking more social. 🧠💖

Administered by:

Server stats:

1.2K
active users

#database

18 posts16 participants2 posts today

Some time ago I mentioned here, in half-joking way, self-fixing software I work with. I said Patroni #Postgres has the best regeneration ability I've ever seen. And currently "the best ability" includes:

> After network migrations servers changed IP addresses. It broke etcd config so I had to completely delete that config and initialize etcd cluster again. Which also forced cleaning and renewing Patroni config because it is strongly dependent on etcd. Even when configuration temporarily didn't exist, connection with WAL archives (technically other separate server) wasn't interrupted (I am not even sure if real data transfer could happen at that time). It was seemingly enough to start new #database cluster from last timeline. I don't know WHAT forced servers to immediately pull that data on fresh start. At migration time there weren't any real production data so I didn't even purposely try to restore anything.

> Not so long time later (and now with real production things) some script tests, causing lots of database changes in relatively short time, beyond former server's capacity, killed master server. Patroni switched as intended and I could work on increasing server's capacity (had to do it live, not very convenient). First server finally decided data corruption was too big and to fix it automatically deleted whole /var/lib/postgresql/* directory and started to recreate thing from scratch, using data from new master server (and was doing it with at least 2 GB/s speed because why not? :blobcatjoy:).

> During above mentioned process impatient tester hit again with their not optimised scripts, finally killing whole cluster. Swearing silently I increased remaining servers as it was only thing I really could do. Postgresql API mostly wasn't responsive, it had limited info about last state before final failure. It wasn't possible to force any change or affect it in any way.
First server decided to delete whole directory again and recreate it (at least this time I saw exact moment in logs), at the same time second server did rewind to state of third server (why??). All these things happened automatically, without my help. I wouldn't even know what to do :blobcatsweat:

And it's only beginning when we use it on production. Now I wait for stubborn users to do some more unintended durability tests... Maybe I would see it's even more invincible :blobcatamused:

#admin#sysadmin#it

Check out Kothari Nishchay's session "PostgreSQL pgroll – Zero-Downtime, Reversible Schema Migrations" at #PostgreSQLDayBangkok to explore pgroll, a powerful tool for seamless database migrations.

🔗 Click here youtu.be/uB7egck68Js?si=WD2PXV to watch on the FOSSASIA YouTube channel

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

Watch Michael Paquier's session "AWS and the PostgreSQL Community" at #PostgreSQLDayBangkok to explore how AWS supports the PostgreSQL ecosystem, contributes to its development, and enhances database performance in the cloud.

🔗 Click here youtu.be/1-ds8RtLqt0?si=dTF_RO to watch on the FOSSASIA YouTube channel

youtu.be- YouTubeEnjoy the videos and music you love, upload original content, and share it all with friends, family, and the world on YouTube.

𝐌𝐨𝐧𝐠𝐨𝐃𝐁 𝐒𝐲𝐧𝐜 𝐂𝐨𝐧𝐧𝐞𝐜𝐭𝐨𝐫 𝐀𝐥𝐩𝐡𝐚 5 𝐢𝐬 𝐥𝐢𝐯𝐞 --> We’ve upgraded the MongoDB Connector as part of the ObjectBox Sync trial:

🧾 MongoDB Transactions support
🔍 Improved Change Tracking
🛠 Better Error Handling
📊 Updates to MongoDB Admin Page

--> get the update from your customer folder and let us know what you think

Critical Minerals In Ores (CMiO) Database
--
lnkd.in/gynRjUfn <-- shared USGS publication
--
lnkd.in/gETca3DQ <-- shared link to open data database, web map services, etc
--
portal.ga.gov.au/persona/cmmi <-- shared web map
--
lnkd.in/gdmMp2zg <-- shared editorial piece on critical minerals and geopolitics
--
#geology #fedscience #opendata #CMMI #CMiO #criticalminerals #minerals #ores #database #opendata #GIS #spatial #mapping #spatialanalysis #commodities #technology #components #geochemistry #deposits #mining #extraction #classifaction #nomenclature #environments #structuralgeology #exploration
@USGS | @GeoscienceAustralia | @GeologicalSurveyOfCanada

Today I'm researching better workflows to backup databases, and create sanitised copies for local development.

I'm not able to find a great deal of informative discussion around best practice.

Is this stuff more obvious than I think - or is it so under-the-radar-unsexy that industry practice is just not very good?

PostgreSQL Shared Libraries: Solving Python Extension Library Path Issues
Smoothly integrate Python extensions with PostgreSQL Shared Libraries, especially when using NumPy. Properly configuring the `shared_libraries` parameter prevents runtime errors by ensuring your database server can locate necessary libraries. Learn how to manage PostgreSQL Shared Libraries for robust Python extensions! #PostgreSQL #Python #SharedLibraries #NumPy #Database #Extensions
tech-champion.com/databas...