Apparently the 2038 problem was fixed in #MariaDB 2 months ago, and considering the last time I checked up on this there were literally no plans to fix it ever, and some of the projects I've built do have date values beyond 2038 ('lifetime' accounts that expire in 2100 etc ), I'm genuinely a bit relieved about this one!

Absolutely no idea what the status of this is in anything other than MariaDB mind. That's going to be a fun year as a #Gentoo #Linux guy isn't it?

Don’t miss tomorrow’s webinar on what’s new in #MariaDB 11.8 LTS—features, improvements, and why it matters for your apps.

Register now and join us live: https://go.mariadb.com/25Q2-WBN-GLBL-Community11.8-2025-06-25_Registration-LP.html

I'm just starting to look into it myself, but maybe somebody has already seen this:

I have a #MariaDB / #Galera cluster with 500 million records, one single table. If I look up an entry via primary key, it returns in <100ms. If I run a `select count(id) from...` it takes over three minutes.

What should I look into? Even if the index is not in memory, it should not take that long to collect the data in the cluster from the slow storage, should it?

Usage of MariaDB Auto Upgrade #MariaDB
https://blog.martinscloud.com/mariadb-the-usage-of-mariadb_auto_upgrade/

This is just beautiful. The project uses #MariaDB to store all the collected data. It makes heavy use of #API endpoints which will be a top priority not only for the internal workings. My focus mostly lies in making this as flexible as possible so people can configure it exactly as they need it. Configuration will be in #yaml.

What i got so far is:

• packet capturing (from client, sent to the control server)
• a webhook (which will be a drop-in replacement for #Discord's since a lot of services support sending logs to discord webhooks)

What's planned:

• Log file monitoring (like #Fail2Ban, but more advanced and easier to configure)
• A fully featured dashboard which visualizes the data and gives you control and a transparent overview of your network activity.
• IP banning (multiple ways to make it flexible)
• Maybe even some advanced responses (like reporting all ports as open for nmap scans)

I would be very interested to know what you think. Ideas, criticism and questions are very welcome. As soon as the base is working, i will push it to #Github.

Galera Cluster acquired by @mariadb
https://www.admin-magazine.com/News/MariaDB-Acquires-Galera-Cluster?utm_source=mam
#MariaDB #GaleraCluster #Codership #database #enterprise #HighAvailability

Klickste dich ganz unschuldig durch deine Infrastuktur, fällt dir so ein #Percona 5.7 Server auf die Füße...

WTF?!

Wie viele Jahre ist das Ding jetzt unterm Schirm geflogen xD

War war ein Kampf, aber ist jetzt auf #MariaDB 11.4 LTS migriert.
Komisches Charset.

Oookay, ist halt doch wichtig immer mal wieder einfach so zu schauen^^

MariaDB 11.8 LTS open-source RDBMS is out, featuring full MariaDB Vector support, faster backups, improved replication, and more.
https://linuxiac.com/mariadb-11-8-lts-rdbms-lands-with-vector-search/

#Roundcube 1.5.10 (#LTS) has been released (#Webmail / #Mail / #IMAP / #SMTP / #LDAP / #Managesieve / #PHP / #MariaDB / #MySQL / #PostgreSQL / #SQLite / #OracleDB / #MSSQL / #LongTermSupport) https://roundcube.net/

#Roundcube 1.6.11 (stable) has been released (#Webmail / #Mail / #IMAP / #SMTP / #LDAP / #Managesieve / #PHP / #MariaDB / #MySQL / #PostgreSQL / #SQLite / #OracleDB / #MSSQL) https://roundcube.net/

Another day, another vagrant-libvirt setup.

This time for MariaDB, with a server VM and a client VM. As usual, vagrant, libvirt and Ansible do the heavy lifting.

https://codeberg.org/johanneskastl/mariadb_vagrant_libvirt_ansible
https://github.com/johanneskastl/mariadb_vagrant_libvirt_ansible

Have a lot of fun...

It would be cool to have a column in a #mariadb #mysql table that auto-enum-ed. SELECTs would work like they do for ENUM() but INSERTs and UPDATEs would add new values to the ENUM() as they arrive.

Another way to describe this would be to automatically normalise a column such that you read/write it like a non-normalised field but on write it checks for that value in a table of unique values and stores a ref. It would need garbage collection on the referenced table.

Troubleshooting the friendica.world issues.. today looking at the database.

Not one of my favourite things, query tuning..