Database Technology

SAG2 introduces a multi-hop retrieval architecture that eliminates the need for dense embeddings and complex database infrastructure. By leveraging a single SQLite database with BM25 lexical indexing, it shifts semantic evidence selection to query time. This approach removes dependencies on offline embedding computation and dedicated database servers, simplifying deployment while maintaining retrieval capabilities.

• Eliminates offline embedding computation and dense index maintenance
• Uses a single SQLite database instead of dedicated database servers
• Shifts semantic evidence selection to query time using BM25 and JEV
• Simplifies infrastructure by removing LLM-based event-entity extraction
• Enables practical multi-hop retrieval without complex corpus preparation

Amazon Redshift now supports long-term retention of system table data by natively integrating with Amazon S3 Tables in additional regions. This feature allows data to be automatically exported to Apache Iceberg format, bypassing the traditional seven-day storage limit for monitoring and audit logs. The service handles all partitioning and compaction tasks, removing the need for custom ETL pipelines to archive this data.

• Extends system table data retention beyond the default 7-day window for compliance needs
• Automatically exports data to S3 Tables in Apache Iceberg format
• Eliminates custom ETL pipelines and reduces resource contention on production clusters
• AWS manages partitioning, compaction, and retention policies natively

Fleet impact: Review Redshift cluster configurations to enable S3 Tables integration, eliminating brittle custom ETL scripts for long-term audit log retention while ensuring compliance data remains queryable without impacting production performance.

The pgBackRest community has released version 2.60.0 of their popular backup and restore tool for PostgreSQL. This update continues to support scalable, reliable backup infrastructure with features like parallel operations, incremental backups, and multi-cloud storage integration.

• Latest stable release of pgBackRest for PostgreSQL backup management
• Supports parallel backup/restore and incremental backup strategies
• Includes ransomware protection and checksum validation capabilities
• Compatible with S3, Azure, GCS, and SFTP storage backends
• Enables backup from standby servers and partial backup resume

Fleet impact: For fleets running PostgreSQL on AWS RDS or Aurora, verify pgBackRest 2.60.0 compatibility with your current PostgreSQL versions and storage configurations. Check if the new ransomware protection and checksum validation features can enhance your existing backup strategy without performance impact.

Hubert 'depesz' Lubaczewski investigates a claim that storing only changed columns in audit logs yields smaller tables but slower triggers. He notes the original post lacked schema details and test methodology, prompting a personal replication to verify the performance trade-offs.

• Audit logging strategy: full-row vs. column-diff impacts storage and CPU
• Original claim: column-diff logs are 5x smaller but trigger execution is slower
• Reproduction requires specific schema context; original post omitted details
• Performance tuning of audit triggers depends heavily on row width and change frequency

Fleet impact: Review audit trigger implementations on high-churn ExaCC or RDS tables to determine if column-diff logging introduces unacceptable CPU overhead compared to the storage savings.

The upcoming November 2026 PostgreSQL hacking workshop will feature Álvaro Herrera discussing the correct implementation of table repacking. Participants can register via the provided form to receive an invitation to the session.

• November 2026 workshop focuses on best practices for PostgreSQL table repacking
• Álvaro Herrera leads the discussion on correct repacking methodology
• Registration required via form to secure a spot in the hacking workshop