Database Technology

This AWS Database Blog post details a three-tier architecture combining Amazon ElastiCache for Valkey, an exact-match cache, and Amazon Aurora PostgreSQL to create a membership lookup system. The design leverages Bloom filters for initial screening while ensuring zero false-positive risk through subsequent exact-match verification against the relational source of truth. The approach aims to deliver sub-millisecond decision times at peak throughput by minimizing expensive database hits.

• Eliminates false-positive risk by using exact-match verification after Bloom filter screening.
• Achieves sub-millisecond latency for membership lookups at high throughput.
• Combines Valkey for speed with Aurora PostgreSQL as the authoritative data source.
• Reduces database load by filtering non-existent keys before hitting Aurora.

Percona developed a custom harness to evaluate how well large language models handle specialized database administration workloads. The testing focuses on practical systems-administration tasks executed against remote systems rather than theoretical prompts. This approach aims to measure the actual utility of LLMs in operational database environments.

• Percona built a specific harness to test LLMs on real-world DBA tasks
• Evaluation targets practical systems-administration rather than abstract queries
• Tests run against remote systems to simulate actual operational conditions
• Goal is to determine LLM readiness for specialized database administration

Christophe Pettus explains the introduction of max_notify_queue_pages, a new GUC that enforces a hard limit on the LISTEN/NOTIFY queue size. Previously, this queue, stored as SLRU pages in pg_notify, relied on implicit bounds that ceased to function effectively. This new parameter provides explicit control to prevent unbounded memory consumption in PostgreSQL clusters.

• Explicitly limits LISTEN/NOTIFY queue memory via pg_notify SLRU pages
• Fixes broken self-enforcement from versions prior to PostgreSQL 17
• Prevents runaway memory usage in high-throughput notification scenarios
• Configurable via GUC for operational tuning and stability

The pgAdmin 4 development team released version 9.18, addressing four security vulnerabilities (CVE-2026-86861 through CVE-2026-86864) alongside 29 bug fixes. Key features include a toggleable Object Explorer that mimics VS Code's sidebar behavior and persists state across refreshes. The release also hardens default Content-Security-Policy settings and introduces a customizable keyboard shortcut for toggling the explorer.

• Urgently patch to mitigate four new CVEs affecting pgAdmin 4 installations.
• Adopt the new toggle_object_explorer preference for faster UI navigation.
• Review Content-Security-Policy changes to ensure no dependency breakage.
• Update to v9.18 to resolve 29 assorted bugs and stability issues.

The fourth alpha release of pgColumnar focuses on improving data layout and query skipping capabilities. It introduces Hilbert curve-based table layout to keep neighboring keys closer together compared to Z-ordering. Additionally, the release enhances star-schema joins by enabling the skipping of fact-table groups during execution.

• Hilbert curve layout offers better locality than Z-ordering for neighboring keys.
• Star-schema joins now support skipping fact-table groups for improved performance.
• This alpha release targets layout efficiency and query execution optimization.
• pgColumnar continues to evolve as a columnar access method for PostgreSQL.

PostgreSQL 19's release cycle encountered significant delays due to an aggressive pace that saw eight major features land in the five weeks preceding the code freeze. The intense development pressure led to three committers withdrawing their contributions, causing the release process to falter under its own scope. This highlights the risks associated with compressing large-scale feature integration into tight pre-freeze windows.

• PostgreSQL 19 release is delayed or unstable due to scope creep.
• Eight major features merged late, destabilizing the freeze period.
• Three committers withdrew work, indicating burnout or quality concerns.
• Late-merge risk management is critical for major version stability.