A TacitSoft database publication
The operator signal behind faster queries, safer migrations, recoverable backups, and databases that stay boring in production.
Edition September 19, 2026
8 source-linked stories · UTC
Planet for the MySQL Community · mysql mariadb community
♦ MariaDB Community Server 13.0 has reached General Availability (GA) and is now officially stable. This release introduces a range of new features, deprecations, and performance improvements, including expanded support for procedural SQL, new DML capabilities, and more. By Sergio De Simone
Read the source →MariaDB Foundation · mariadb official
At Percona Live Amsterdam I caught up with Sveta Smirnova , a world-renowned MySQL expert, author of “MySQL Troubleshooting” and “MySQL Cookbook, 4th Edition”, and a frequent speaker at events from Oracle OpenWorld and FOSDEM to HighLoad. … Continue reading \"“Verify, Measure, and Get Your Hands Dirty”: Two Decades of Database Support with Sveta Smirnova\" “Verify, Measure, and Get Your Hands Dirty”: Two Decades of Database Support with Sveta Smirnova appeared first on MariaDB.org
Read the source →PlanetScale · mysql postgresql engineering
Meet Neki: sharding for Postgres. Neki allows applications to connect to massive, sharded databases over a single connection string. This post takes apart the architecture from the bottom up, one piece at a time, starting with what's underneath all of it. Real Postgres Neki is built as a sharding and scaling solution for real Postgres. It's not a fork, nor a wire-compatible reimplementation, nor a MySQL sharding idea wearing a Postgres label. Neki uses ordinary PostgreSQL instances that store rows in Postgres data pages using MVCC, carry out transactions, and work as you would expect with psql and other Postgres drivers. Neki builds around those instances to let you shard them, scale them, and manage them as one database. Let's take a look: PostgresManager Using vanilla Postgres means Neki
Read the source →ClickHouse · analytics database
Notes from three days in the Netherlands, featuring a lightning talk on pg_clickhouse and pg_stat_ch at PGDay Lowlands and a session on PostgreSQL 19 monitoring at Percona Live Amsterdam.
Read the source →Planet PostgreSQL · postgresql community
postgres.scot is live Postgres events in Scotland now have a permanent address: postgres.scot It is a deliberately small page. Right now it points at the PostgreSQL Edinburgh User Group (PostgresEDI) on cloomba , where you will find RSVPs, a calendar subscription and an RSS feed, and it will carry other Scottish Postgres events as they come along. The point is to have one address worth bookmarking and sharing, rather than whichever platform we happen to be on this year. If you are running something Postgres-related in Scotland and want it listed, email info (at) postgres.scot . postgres.scot is a volunteer website, not affiliated with or endorsed by the PostgreSQL project or the PostgreSQL Community Association. The August meetup Thursday, August 13th, Paterson's Land at the University of
Read the source →Planet for the MySQL Community · mysql mariadb community
This September and October, Heather VanCura will meet with MySQL users, contributors, developers, DBAs, customers, and community leaders across Brazil and Europe. With more than 30 years of innovation behind it, the MySQL community is entering an important new phase. The focus is on expanding engagement, collaboration, and contributions while increasing and driving innovati
Read the source →Planet PostgreSQL · postgresql community
I used AI tools to size an OLTP workload on an EC2 system, with DBT-5 , a TPC-E-like fair-use implementation. I provided a systematic and mechanical plan for running a series of tests to determine what the appropriate scale factor is on a system. I pre-configured the database with some settings that are known to be needed to be changed, such as shared_buffers and max_wal_size but more on this at a later time when we characterize the system behavior further to be able to tune some of these settings better. Remember, this is an iterative process when trying to figure it out for any workload. I decided to use Claude Fable 5.1 for this exercise and fed in the following instructions: Start with the minimum valid database size with 5000 customers. Start testing with 1 user and increase by 1 user
Read the source →DuckDB · analytical database
When DuckDB-Wasm was launched in 2021, databases could not be persisted: everything lived in the Wasm heap and vanished when the tab closed. Keeping data meant serializing tables to Parquet, storing the bytes in IndexedDB, and re-registering them on the next page load. This was doable, but had to be handled at the application layer and was not offered out of the box by DuckDB-Wasm. Modern browsers (since March 2023 ) now ship the Origin Private File System (OPFS) , a per-origin, sandboxed file system with random-access reads and writes. DuckDB-Wasm (tested with versions 1.32.0 and 1.33.1-dev64.0) can use it as a storage backend, as described in the DuckDB documentation : a database opened at an opfs:// path survives reloads and browser restarts. The following call opens a database file in
Read the source →