database

EF Core 11 optimizes split queries by removing unnecessary JOINs of reference navigations from collection queries, reducing database overhead and improving performance.

The article discusses the performance of MongoDB's vector search capabilities, likely comparing it to other solutions or highlighting improvements for AI workloads.

Extralite 3.0.0, a fast Ruby SQLite wrapper, introduces object graph transforms and modern defaults for database interaction.

GreptimeDB v1.1.2 is a patch release that fixes scheduled Flows now() binding for deterministic EVAL INTERVAL windows, along with bug fixes for Kafka SASL password redaction, GC index file listing, parquet metadata cache size, Prometheus label discovery scan, and PromQL time binary aggregation. It is recommended for users to upgrade.

LMDB 1.0 is a high-performance, transactional key-value store database library with ACID semantics, memory-mapped storage, and full thread/process safety. The new version includes upgrades from 0.9 and continues to offer a simple, robust embedded database solution.

PostgreSQL 19 introduces kernel asynchronous reads via io_uring, enabling direct asynchronous buffered I/O for improved performance without dedicated worker processes.

Tobi recommends using Ducklake with DuckDB for efficient data import, such as health data from Fitbit, and suggests telling agents to learn it.

chDB is a complete ClickHouse OLAP engine compiled to WebAssembly, enabling SQL queries directly in the browser via a SQL shell at wasm.chdb.io.

GreptimeDB improved distributed query performance by enabling remote dynamic filters to push down to datanode scans at runtime and optimizing the optimizer to run before MergeScan wraps remote plans, ensuring filters reach the data. JSON v2 columns now support type hints.

This article discusses common pitfalls in database partitioning, particularly the mistake of partitioning by a date column that forces queries to include a date filter. It proposes partitioning by the primary key instead and using a background service to manage partition boundaries, thus avoiding the need to modify application code.

The author argues that ORMs are more detrimental than beneficial and that developers should focus on learning SQL directly to avoid issues like attribute creep and inefficient queries.

Canonical's dqlite team used TLA+ to model and understand a 16-year-old SQLite bug in WAL checkpointing that can cause database corruption, then verified whether dqlite is affected.

Kronotop explains its architecture for handling thousands of concurrent connections with blocking I/O by separating connection management (using Netty event loops) from work execution (using Java virtual threads), allowing it to scale like Redis while supporting blocking operations like FoundationDB calls.

PlanetScale introduces Database Traffic Control, a Postgres traffic management system that lets users enforce flexible budgets on database resources, preventing overload from bad queries or runaway workloads.

A blog post discussing how performance improvements that fail to cross the 10-second attention threshold may not yield user experience benefits, using examples from database query optimization and process automation.

Someone on GitHub open-sourced a database of 1,324 fitness exercises, each with images, GIF animations, bilingual instructions, target muscles, and equipment type, along with a directly runnable local webpage and developer tools, suitable for fitness app prototypes, AI motion recognition, etc.

A project to build a faithful implementation of the 1976 MUMPS standard, including a parser, interpreter, and integrated hierarchical database, to study the original architecture and run historical software from the era.

The TiDB Cloud team built an AI Agent cloud disk called drive9.ai based on TiDB, aiming to provide a queryable, programmable, and governable file system layer for Agents, solving engineering pain points such as file and metadata consistency, object storage latency, and file understanding in AI scenarios.

pg_plan_advice is a PostgreSQL module that allows users to influence and stabilize query plan choices by specifying plan advice using a mini-language. It helps in controlling join order, scan methods, and other planner decisions, but overriding planner defaults can backfire if data distribution changes.

This paper introduces logical physical clocks and methods for consistent snapshots in globally distributed databases, addressing causality and consistency challenges.