OffNet Newsroom

Daily topic roundup

Database Technology

Wednesday, August 26, 2026 · 8 stories, curated & summarized — click any story for the source.

Amazon RDS for PostgreSQL now offers support for the latest minor releases across versions 14 through 18. These updates address Common Vulnerabilities and Exposures (CVEs) and include community bug fixes and performance improvements. AWS recommends upgrading during scheduled maintenance windows to ensure security and stability.

  • Upgrade to address CVEs and gain access to the latest PostgreSQL bug fixes.
  • Use automatic minor version upgrades during scheduled maintenance for seamless updates.
  • Leverage AWS Organizations Upgrade Rollout Policy to orchestrate phased upgrades at scale.
  • Minimize downtime by utilizing Amazon RDS Blue/Green deployments for critical databases.

Fleet impact: Update your RDS PostgreSQL instances to the latest minor versions to patch security vulnerabilities and resolve known bugs. Enable automatic minor version upgrades in your maintenance windows to ensure consistent patching across your fleet.

CHECKLISTWhat matters hereUpgrade to address CVEs and gain access to the latest PostgreSQL bug…Use automatic minor version upgrades during scheduled maintenance for…Leverage AWS Organizations Upgrade Rollout Policy to orchestrate…Minimize downtime by utilizing Amazon RDS Blue/Green deployments for…

A Percona support case reveals that PostgreSQL standby lag on AWS FSx can stem from EC2 single-flow bandwidth caps rather than storage performance. The issue occurs when network throughput for a single TCP connection hits limits, stalling WAL shipping. This highlights a hidden constraint in how EC2 instances handle high-bandwidth, single-stream traffic to FSx.

  • Check EC2 network bandwidth limits for single-flow connections when diagnosing FSx lag.
  • High-WAL-volume standbys may hit single-connection throttles before storage bottlenecks.
  • Monitor network metrics, not just IOPS, to identify replication stalls on FSx.
  • Consider multi-connection strategies or instance upgrades if single-flow limits are hit.
CHECKLISTFSx Lag Troubleshooting StepsCheck EC2 single-flow bandwidth limits for replication lagMonitor network metrics, not just IOPS, for stallsConsider multi-connection strategies if single-flow limits are hit

PostgreSQL 19 introduces the WAIT FOR SQL command, allowing sessions to block until WAL reaches a specific Log Sequence Number (LSN). This mechanism enables read-your-writes consistency on asynchronous replicas without requiring synchronous replication. The command supports options for mode, timeout, and error handling via NO_THROW.

  • Enables read-your-writes consistency on async replicas by waiting for WAL positioning.
  • Eliminates the need for synchronous replication overhead to achieve strong consistency.
  • New SQL syntax: WAIT FOR LSN 'lsn' WITH (mode, timeout, no_throw options).
  • Provides a practical alternative to synchronous replication for consistency-critical apps.
  • Requires PostgreSQL 19 to utilize the new WAIT FOR command functionality.

Channel Corporation resolved transaction-conflict throttling by splitting a monolithic DynamoDB User table into role-specific tables and isolating Badge data in a dedicated UserBadge table. This architectural change eliminated GSI back pressure caused by high-write contention on the original wide table. The team executed a zero-downtime online migration of the data using DynamoDB Export and Import alongside Amazon S3 and AWS Glue.

  • Splitting wide tables by access pattern reduces write contention and prevents GSI back pressure.
  • Isolating high-churn attributes like badges into separate tables minimizes transaction conflicts.
  • DynamoDB Export/Import with S3 and Glue enables zero-downtime migration for large datasets.
  • Role-specific table design improves throughput stability for diverse user workloads.

PostgreSQL 18 introduces three new GUCs—log_connections, log_disconnections, and log_hostname—to provide finer control over connection audit trails. These settings allow administrators to selectively log when sessions start and end, along with the client's hostname. This granularity helps reduce noise in logs while maintaining visibility into connection patterns for security and debugging.

  • New GUCs log_connections and log_disconnections offer targeted session audit capabilities
  • log_hostname enables automatic inclusion of client hostnames in connection logs
  • PostgreSQL 18 is the first version to support this granular connection logging
  • Useful for reducing log noise while maintaining security visibility in production

DuckDB Labs has previewed version 2.0, codenamed Cyanoptera, featuring over 10,000 commits. The release introduces a client/server mode that enables network connections, shifting the architecture beyond its traditional embedded model. Additional updates include extension portability, advanced data types, a new parser, and performance gains via asynchronous I/O and storage optimizations.

  • Client/server mode enables network connections, moving beyond the embedded-only paradigm.
  • Over 10,000 commits signal a major architectural shift toward distributed capabilities.
  • Asynchronous I/O and storage optimizations provide significant performance improvements.
  • General availability is targeted for fall 2026, allowing time for evaluation.
  • New parser and advanced data types enhance extensibility and data handling.
Hacker News (100+ points) general

Queryable Executables: Embed Structured Metadata in Binaries

Fahad Zakaria proposes embedding structured, queryable metadata directly into compiled executables, moving beyond simple string tags. This approach allows tools to inspect binary contents for provenance, build configurations, and dependencies without relying on external sidecars or separate manifest files. The technique aims to solve the 'black box' problem in modern software delivery by making binary introspection first-class.

  • Eliminates reliance on external SBOMs by embedding provenance data directly in the binary.
  • Enables automated tooling to verify build arguments and dependency trees at runtime.
  • Reduces supply chain risk by making binary contents self-describing and queryable.
  • Simplifies debugging by attaching build context to the artifact without extra files.
WORTH QUOTINGThe gist“Fahad Zakaria proposes embedding structured, queryablemetadata directly into compiled executables, moving beyondsimple— Hacker News (100+ points)
AWS What's New awsdatabase

Amazon RDS for SQL Server now supports SQL Server 2025 CU6

Amazon RDS for SQL Server has added support for the latest Microsoft Cumulative Update, specifically SQL Server 2025 CU6 (KB5093421). This update corresponds to RDS engine version 17.00.4055.5.v1 and contains various improvements and fixes detailed in the Microsoft documentation. Administrators are encouraged to upgrade their DB instances via the AWS Management Console, CLI, or SDK to apply these patches.

  • RDS SQL Server engine version 17.00.4055.5.v1 now includes SQL Server 2025 CU6.
  • Apply updates via AWS Console, CLI, or SDK to ensure instances are patched.
  • Review Microsoft KB5093421 for specific bug fixes and feature improvements.
  • Schedule maintenance windows to minimize downtime during the upgrade process.
CHECKLISTApply SQL Server 2025 CU6Upgrade to RDS engine version 17.00.4055.5.v1Apply patches via Console, CLI, or SDKReview Microsoft KB5093421 for fixesSchedule maintenance windows to minimize downtime
↑