Database Technology

This paper introduces BudgetSchemaBench, a diagnostic framework for optimizing database schema injection into LLM context windows. Using an 80-database catalog, the authors sweep four schema-context budgets to compare representation strategies while maintaining fixed table ranking. The benchmark mechanically derives relevance labels from gold SQL, eliminating the need for human or LLM-generated ground truth and including a namespace check to prevent cross-database result leakage.

• Schema serialization costs force trade-offs between table coverage and detail before context limits are hit.
• Relevance labels are derived mechanically from gold SQL, removing human/LLM annotation bias.
• Namespace checks ensure queries return correct results from the intended source database only.
• Evaluation sweeps four context budgets against three schema representations with fixed retrieval ranking.

Pgpool-II has issued maintenance releases across five versions, addressing critical security vulnerabilities. CVE-2026-92867 allows an attacker to write arbitrary 32-bit values to memory via malformed watchdog messages during failover. Additionally, certificate authentication fails to properly handle NUL bytes in client X.509 certificate Common Name fields.

• Apply updates immediately to fix CVE-2026-92867 memory corruption risk.
• Update Pgpool-II to mitigate NUL byte handling in client certificates.
• Affected versions: 4.7.3, 4.6.8, 4.5.13, 4.4.18, and 4.3.21.
• Monitor failover logs for potential watchdog message injection attempts.

Tomas Vondra clarifies that recent Postgres 19 feature reverts were not caused by AI-discovered bugs, contrary to circulating reports. The delays stem from invasive fix requirements late in the development cycle, pushing the release back by approximately one month. This correction aims to address misconceptions about the specific technical drivers behind the schedule slip.

• Postgres 19 release is delayed by ~1 month due to late-cycle reverts
• Vondra rejects claims that AI tooling directly caused the patch reversals
• Reverted features required invasive fixes incompatible with current cycle
• Practitioners should monitor for updated release candidate timelines
• Development focus shifts to stabilizing remaining core components

Amazon Redshift has added a DEBUG permission that allows specific identities to view unredacted secure logging records across multiple data warehouses. This change addresses the visibility gap created by Federated Permissions, which previously redacted sensitive values in system tables to protect data owners' information. Data owners can now grant auditors and administrators the necessary access to troubleshoot and audit queries without compromising data security.

• DEBUG permission enables unredacted log access for authorized troubleshooters.
• Logging remains redacted by default to protect FGAC-protected data.
• Permissions apply automatically across all warehouses in the AWS account.
• Simplifies auditing of rewritten query text and error messages.

Percona has published guidance on optimizing ClusterSync for MongoDB, which replicates data from source clusters like Atlas to targets in two phases. The process begins by establishing a consistent starting point and cloning collections and indexes while simultaneously capturing changes via MongoDB change streams. Once the initial copy finishes, the tool transitions to replicating ongoing changes.

• ClusterSync uses a two-stage replication model for MongoDB data synchronization.
• Initial phase clones collections and indexes while capturing change streams.
• Post-clone phase handles ongoing replication of source database changes.
• Source clusters can include on-prem MongoDB or MongoDB Atlas deployments.