DuckDB Client-Server Protocol, v1.5.3 Release, and pg_timetable Migration
Today's Highlights
This week's highlights include DuckDB's foundational Quack client-server protocol and its 1.5.3 release, which significantly expands features through upgraded extensions. We also cover a practical guide to migrating PostgreSQL job scheduling from pgAgent to the more modern pg_timetable.
Quack: The DuckDB Client-Server Protocol (DuckDB Blog)
Source: https://duckdb.org/2026/05/12/quack-remote-protocol.html
DuckDB has introduced Quack, a new remote protocol that enables client-server functionality for the popular embedded analytical database. Historically, DuckDB operated purely as an in-process, embedded solution, but Quack changes this by allowing DuckDB instances to communicate, supporting multiple concurrent writers to a single database.
The protocol is designed with DuckDB's core principles of simplicity and efficiency, utilizing Flatbuffers for its message format to ensure high-performance serialization and deserialization. It supports various transports, including HTTP, and aims to be flexible for future implementations like WebSockets or QUIC. This development is a significant step, moving DuckDB beyond purely embedded use cases and opening doors for more complex, distributed analytical architectures where concurrent access and remote operations are critical.
Comment: The Quack protocol fundamentally transforms how DuckDB can be deployed, making it suitable for server-side applications requiring multi-user access and concurrent writes. This is a game-changer for developers looking to scale their DuckDB solutions beyond single-process limitations.
DuckDB 1.5.3: Not an Ordinary Patch Release (DuckDB Blog)
Source: https://duckdb.org/2026/05/20/announcing-duckdb-153.html
DuckDB has announced the release of version v1.5.3, which, despite being a patch release, brings a wealth of new features primarily through substantial upgrades to its extensions. While the core database sees limited bug fixes, the enhanced extensions deliver significant new capabilities to users.
Key highlights from this release include the integration of the new Quack client-server protocol (detailed separately), improved spatial data capabilities, and expanded options for reading Parquet and CSV files. The release underscores DuckDB's modular architecture, allowing extensions to evolve rapidly and bring advanced functionalities like new JSON processing features or enhanced HTTP file system support. This strategy ensures users receive a continuous stream of innovative features without needing to wait for major core version updates, solidifying DuckDB's position as a versatile tool for data analytics.
Comment: This 'patch' release demonstrates DuckDB's effective strategy of leveraging its extension ecosystem for rapid feature delivery. The upgraded extensions, including the new Quack protocol, provide immediate, tangible benefits to users, making 1.5.3 a surprisingly significant update.
Replacing pgAgent with pg_timetable: Part 1 (Planet PostgreSQL)
Source: https://postgr.es/p/9mC
Regina Obe addresses the impending retirement of pgAgent, a long-standing scheduling solution for PostgreSQL, within the next six months, along with the discontinuation of its UI in pgAdmin. In 'Part 1' of her series, she introduces pg_timetable as a robust and modern alternative for managing scheduled tasks within PostgreSQL.
The article outlines the compelling reasons for choosing pg_timetable, highlighting its native implementation in PL/pgSQL, support for distributed queues, and sophisticated features like cron-style scheduling, recurrent tasks, and advanced error handling. It positions pg_timetable as a powerful, database-centric solution for automating routine database maintenance, data pipeline operations, and other time-based tasks. The post provides practical guidance on the initial setup and configuration, making it an invaluable resource for administrators and developers facing the transition away from pgAgent.
Comment: Given pgAgent's deprecation, adopting pg_timetable is a timely and necessary migration for many PostgreSQL users. This guide offers a practical starting point for transitioning to a more capable, native job scheduler that aligns with modern PostgreSQL workflows.
Top comments (0)