OffNet Newsroom

Daily topic roundup

Database Technology

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

Share this roundup on LinkedIn Full edition
Planet PostgreSQL database

PostgreSQL GUC: hash_mem_multiplier separates hash and sort memory budgets

Christophe Pettus introduces hash_mem_multiplier, a new GUC that decouples memory allocation for hash and sort operations. This allows practitioners to tune these distinct workloads independently, addressing the previously coupled resource constraints. The change enables more precise control over memory usage for specific query patterns.

  • Decouples hash and sort memory limits for finer-grained tuning.
  • Resolves contention where one operation starved the other.
  • Enables targeted optimization for mixed hash/sort workloads.
  • New GUC requires explicit configuration to activate separate budgets.
  • Improves predictability for memory-intensive query execution plans.
Read at source →
AWS Database Blog awsdatabase

AWS Aurora DSQL: Design patterns for scalable, ACID-compliant distributed apps

The AWS Database Blog outlines practical guidance for designing applications that scale effectively with the Amazon Aurora DSQL distributed architecture. It details how to identify scalability bottlenecks and apply proven design patterns, including optimized primary key selection, schema design, and indexing strategies. The post emphasizes maintaining full ACID compliance across multiple AWS regions while distributing workloads efficiently.

  • Select primary keys and design schemas to minimize cross-partition latency in distributed environments.
  • Apply indexing strategies that support efficient distributed query execution without sacrificing write throughput.
  • Implement transaction strategies that preserve ACID guarantees across multiple AWS Regions.
  • Identify common application patterns that limit scalability before migrating to or designing for DSQL.
Read at source →
Planet PostgreSQL database

PostgreSQL 11-18 SQL Feature Selection: Key Improvements for Developers

Dimitri Fontaine reviews seven major PostgreSQL releases from 2018 to 2025, selecting user-visible SQL enhancements that address standard gaps and refine functionality. The curated list highlights features that proved essential while rewriting examples for a new book edition. Each release contributed significantly to the SQL layer, improving performance, replication, and administration capabilities.

  • Covers seven annual releases (11-18) with 150-200 user-visible changes each.
  • Focuses on SQL layer improvements, standard compliance, and rough edge cleanup.
  • Features selected based on practical utility during book example rewrites.
  • Organized by theme with specific version indicators for easy reference.
  • Validated against the F1 database in the free Planet PostgreSQL Lab dataset.
COMPARISONPostgreSQL 11-18 ChangesMin changes150Max changes200
Read at source →
AWS What's New awsdatabase

S3 Tables adds Variant type for schema-less Iceberg V3 JSON writes

Amazon S3 Tables now support the Variant data type per the Apache Iceberg V3 specification, enabling direct ingestion of semi-structured JSON without pre-defined schemas. Iceberg V3 engines automatically shred this data into hidden columns, generating Parquet statistics that facilitate file pruning and optimized query performance. The service also handles ongoing maintenance like compaction to consolidate small files into larger, more efficient reads for Variant columns.

  • Ingest JSON directly into S3 Tables without upfront schema definition.
  • Iceberg V3 engines shred Variant data into hidden columns for stats.
  • Parquet stats enable efficient file pruning during analytical queries.
  • Automatic compaction consolidates small Variant files for better reads.
HOW IT WORKSVariant Data Pipeline1Ingest schema-less JSON2Shred into hidden columns3Generate Parquet statistics4Enable file pruning5Consolidate via compaction
Read at source →
AWS Database Blog awsdatabase

AWS RDS SQL Server: Diagnosing Query Performance with CloudWatch and Query Store

AWS details a workflow for monitoring and resolving T-SQL performance issues on Amazon RDS for SQL Server. The approach combines CloudWatch Database Insights, Query Store, and Resource Governor to identify regressions and plan changes. It specifically helps isolate analytical workloads to prevent them from impacting transactional performance.

  • Use CloudWatch Database Insights to detect performance regressions quickly.
  • Leverage Query Store to analyze and compare execution plan changes over time.
  • Apply Resource Governor to isolate and throttle heavy analytical workloads.
  • Combine these tools for a complete diagnostic workflow on RDS SQL Server.

Fleet impact: For DBAs managing SQL Server on RDS, this integrated approach allows for faster root cause analysis of query regressions without manual server access. Plan to implement Query Store and Resource Governor policies to proactively manage workload isolation and prevent analytical jobs from degrading transactional performance.

Read at source →
AWS Database Blog awsdatabase

AWS introduces automated PII redaction for RDS PostgreSQL audit logs

AWS now offers a serverless pipeline to irreversibly redact personally identifiable information from Amazon RDS for PostgreSQL audit logs. The process removes over 30 data types, including SSNs and credit card numbers, before archiving clean logs to Amazon S3. Users can then query the sanitized data directly using Amazon Athena.

  • Automated redaction handles 30+ PII types like SSNs, emails, and names.
  • Pipeline is serverless, reducing operational overhead for log sanitization.
  • Clean logs are stored in S3 and queryable via Amazon Athena.
  • Redaction is irreversible, ensuring compliance with privacy regulations.
Read at source →
Planet PostgreSQL database

PostgreSQL 19 introduces data lineage to trace financial data origins

PostgreSQL 19 introduces native data lineage capabilities to resolve the common engineering challenge of tracing data origins across complex ETL pipelines. The feature addresses the difficulty of auditing data transformations when documentation is sparse or pipelines were built by former staff. By providing clear visibility into how data flows through views and tables, it simplifies answering specific queries about data provenance for stakeholders.

  • PostgreSQL 19 adds native support for tracking data lineage across transformations.
  • Reduces time spent debugging data discrepancies in legacy ETL pipelines.
  • Simplifies answering audit questions from finance or compliance teams.
  • Eliminates the need for manual grep-based tracing of complex view dependencies.
CHECKLISTData Lineage BenefitsTrack data lineage across transformationsReduce ETL debugging timeSimplify financial audit responses
Read at source →
arXiv cs.CL researchllm

SymCA: LLM Symbolizes Decision Process for Interpretable Column Annotation

SymCA addresses interpretability and accuracy gaps in column annotation by materializing the process as a global-to-local symbolic decision path. The framework uses global skeleton induction to build a semantic structure over label spaces before refining details locally. This approach moves away from direct neural mapping to preserve label semantics and model adaptivity. The method aims to improve annotation quality by making the reasoning traceable rather than opaque.

  • Replaces black-box neural mapping with a symbolic decision process for better transparency.
  • Uses global skeleton induction to structure label semantics before local refinement.
  • Aims to resolve accuracy limits caused by overlooked label semantics in prior models.
  • Enhances adaptivity by maintaining interpretability throughout the annotation pipeline.
HOW IT WORKSSymCA Annotation Pipeline1Global skeleton induction2Build semantic structure3Local detail refinement4Interpretable output
Read at source →
↑