Database Technology

Ambiguity in user queries is a major cause of failure in text-to-SQL systems, often leading to silent deviations from intent. The ARCS paper proposes structured disambiguation, replacing inefficient free-form dialogue with explicit, constrained interactions to resolve these issues. To support this paradigm, the authors introduce the Ambiguity Resolution Corpus for SQL, the first benchmark featuring naturally occurring unconstrained ambiguities.

• Structured disambiguation offers a more efficient alternative to conversational clarification for resolving query ambiguity.
• ARCS benchmark provides the first dataset of naturally occurring, unconstrained ambiguities in text-to-SQL tasks.
• Constrained interactions align better with real-world user workflows than free-form dialogue.
• This approach targets silent errors that cause system outputs to deviate from true user intent.

Dimitri Fontaine outlines how Postgres logical replication enables database consolidation by evolving the feature set across ten releases. This article serves as the second part of a series, assuming readers have reviewed the hub-and-workers architecture for write scalability from Part 1. It focuses on leveraging these capabilities to merge distinct database instances into a unified logical structure.

• Logical replication has matured significantly over ten Postgres releases, enabling complex consolidation patterns.
• Part 1 established a hub-and-workers model; this post builds on that for consolidation use-cases.
• Requires understanding of incremental feature additions across major versions to plan migrations.
• Part 3 will address zero-downtime major upgrades, completing the consolidation lifecycle.

Grab replaced its wide-column database with Aerospike for its high-volume Counter Service, achieving significant performance and cost improvements. The migration involved a redesigned data model that consolidated time buckets into map-based records, supported by shadow traffic and data parity validation. Post-migration metrics show a 50% reduction in p99 read latency, 1 TB disk usage compared to 3 TB previously, and a 45% to 50% drop in cost per node.

• Consolidating time buckets into map-based records reduced storage from 3 TB to 1 TB.
• P99 read latency dropped by approximately 50% after switching to Aerospike.
• Migration strategy used shadow traffic and parity validation to ensure data integrity.
• Cost per node decreased by 45% to 50% with the new storage abstraction.

PostgreSQL extension pg_vault_tde released version 1.7.2 to address critical stability and security issues. The update introduces a new on-disk tuple layout (v5) and fixes segmentation faults occurring during updates on indexed variable-length columns. It also resolves crashes related to TOAST threshold crossings for encrypted values and hardens the tde_btree index to prevent incorrect range query results.

• Upgrade to v1.7.2 to fix critical segfaults on UPDATE operations with indexed variable-length columns.
• New v5 on-disk tuple layout improves walkability and prevents unreadable tables from all-NULL rows.
• tde_btree index now strictly handles equality queries, avoiding incorrect returns on range operations.
• Runtime version check via pg_vault_tde_build_version() distinguishes this binary patch from v1.7.

Percona has released version 1.0.0 of ClusterSync for MongoDB as generally available, marking it as production-ready and fully supported. The tool is designed to facilitate data movement away from MongoDB Atlas, Enterprise, or Community editions. Early validation includes successful migrations involving multi-terabyte datasets.

• Enables migration off MongoDB Atlas, Enterprise, or Community editions.
• Production-ready with full vendor support for enterprise deployments.
• Validated on real-world multi-terabyte migration workloads.
• No longer in beta; safe for critical infrastructure planning.

The pg_ivm 1.16 release adds native support for PostgreSQL 19 and resolves several stability issues in incremental view maintenance. Key fixes address a segfault occurring when an Incremental Materialized View is dropped in the same transaction as maintenance, and correct maintenance failures for tables lacking default equality operators. The update also handles edge cases where OIDs exceed INT_MAX and prevents spurious transaction failures during maintenance operations.

• Upgrade to support PostgreSQL 19 deployments and new features.
• Fixes segfaults when dropping IMVs within the same transaction as maintenance.
• Resolves maintenance failures for tables with types lacking default equality operators.
• Corrects view maintenance when global OID counter exceeds INT_MAX.
• Prevents spurious transaction failures during incremental maintenance runs.