<p><strong>TLDR:</strong> PostgreSQL 18 fundamentally changes what effective_io_concurrency means — it now controls real async I/O depth via a new AIO subsystem, and the default jumped from 1 to 16. Separately, pgAgent is being retired in six months, including its pgAdmin UI, so shops running scheduled jobs need to evaluate pg_timetable or pg_cron now. sqlite-utils 4.0rc1 landed with a built-in migrations system and nested transactions, plus several breaking changes worth reviewing before upgrading. A new LSP for PostgreSQL SQL and PL/pgSQL brings go-to-definition, rename refactoring, and context-aware completion backed by real PostgreSQL grammar.</p>
<hr>
<h2>PostgreSQL 18 rewires effective_io_concurrency into a real async I/O depth control</h2>
<p>This parameter has changed meaning three times across major versions, and PG18 is the biggest shift yet. Before PG13, the value fed a harmonic-series formula tied to spindle counts. PG13 made it a direct I/O request count. PG18 ties it to a new AIO subsystem with io_method options including worker and io_uring — so it now controls actual async read-ahead depth. The default jumped from 1 to 16 to reflect that. Practical guidance: use 16+ on NVMe or cloud storage in PG18, around 200 for SSDs in PG13-17, and never copy a value across major versions without checking which era applies. <a href="https://daily.dev/posts/99XUwF0Xm" target="_blank" rel="noopener nofollow">Read more</a></p>
<h2>pgAgent retiring in six months, pg_timetable and pg_cron are the replacement paths</h2>
<p>pgAgent is being retired along with its pgAdmin UI, which gives shops running PostgreSQL-backed scheduled jobs a hard deadline to migrate. pg_timetable covers most of pgAgent’s feature surface — cross-platform, PostgreSQL as the backend, multiple agents, ordered job steps — but lacks a polished UI. pg_cron is the simpler option if your jobs are SQL-only. Worth noting: the author contributed a patch to make pg_cron compile on Windows via mingw64, so that gap is narrowing. <a href="https://daily.dev/posts/KeuXzePF3" target="_blank" rel="noopener nofollow">Read more</a></p>
<h2>sqlite-utils 4.0rc1 ships migrations and nested transactions with several breaking changes</h2>
<p>The first release candidate for sqlite-utils 4.0 brings two features that matter for anyone using SQLite in production Python projects: a built-in migrations system (ported from the separate sqlite-migrate package) and nested transactions via a new db.atomic() context manager. The breaking changes are worth reading carefully before upgrading — upsert syntax changed to INSERT … ON CONFLICT SET, Python 3.8 support is dropped, the default float column type changed from FLOAT to REAL, and type detection is now on by default for CSV/TSV imports. <a href="https://daily.dev/feed-by-ids?id=vfFby2kab&amp;id=9zqBEF770" target="_blank" rel="noopener nofollow">Read more</a></p>
<h2>postgres-lsp brings IDE-grade tooling to .sql files via real PostgreSQL grammar</h2>
<p>postgres-lsp is a new Language Server Protocol implementation for PostgreSQL SQL and PL/pgSQL, built on tree-sitter-postgres rather than regex heuristics. It covers diagnostics, semantic tokens, go-to-definition, find references, context-aware completion, signature help, rename refactoring, code actions, and SQL formatting with presets for river, mozilla, dbt, and gitlab styles. If you spend meaningful time in .sql files outside a full IDE, this is worth a look. <a href="https://daily.dev/posts/yoK0fzzyU" target="_blank" rel="noopener nofollow">Read more</a></p>
<hr>
<h2>Also notable</h2>
<ul>
<li><strong>PHP PDO driver for DuckDB bundles libduckdb directly into a shared object:</strong> pdo-duckdb-php lets PHP applications query in-memory or file-based DuckDB databases using standard PDO syntax, with support for CSV, JSON, and Parquet files and all DuckDB types — no separate infrastructure required. <a href="https://daily.dev/posts/ppu7QnzbQ" target="_blank" rel="noopener nofollow">Read more</a></li>
<li><strong>T-SQL Analyzer live analysis now covers any SQL script in SSMS 22:</strong> The T-SQL Analyzer extension now runs live analysis on any SQL script in SQL Server Management Studio 22 (not just CREATE statements in Visual Studio), with configurable SQL engine version and rule exceptions via Tools/Options — the SSMS extension requires .NET 10 SDK. <a href="https://daily.dev/posts/wMM37dku6" target="_blank" rel="noopener nofollow">Read more</a></li>
</ul>


Query optimization, schema design, and data store coverage across PostgreSQL, MongoDB, Redis, and more.

Databases Digest

PostgreSQL 18 fundamentally changes the meaning of effective_io_concurrency, tying it to a new AIO subsystem with io_uring support and raising the default from 1 to 16. pgAgent is being retired in six months alongside its pgAdmin UI, with pg_timetable and pg_cron as migration paths. sqlite-utils 4.0rc1 introduces a built-in migrations system and nested transactions via db.atomic(), along with several breaking changes including upsert syntax changes and dropped Python 3.8 support. A new postgres-lsp Language Server Protocol implementation brings IDE-grade tooling to .sql files using real PostgreSQL grammar, covering go-to-definition, rename refactoring, and context-aware completion.

effective_io_concurrency rewired in PG18, pgAgent retirement clock starts