OffNet Newsroom

Daily topic roundup

Database Technology

Friday, July 03, 2026 · 7 stories, curated & summarized — click any story for the source.

Share this roundup on LinkedIn Full edition
Planet PostgreSQL database

Building a RAG Server on pgEdge Cloud via API

Antony Pegg demonstrates how to provision a Retrieval-Augmented Generation server on pgEdge Cloud using the Cloud API rather than the simplified UI. The guide walks through real API calls to configure the service, emphasizing the use of environment variables to keep API keys secure. The example use case involves ingesting data for a GURPS 4th Edition tabletop RPG system.

  • Use the Cloud API for programmatic RAG server provisioning instead of manual UI clicks.
  • Store API keys in environment variables to prevent leakage in shell history.
  • The approach allows for reproducible infrastructure setup via scripted API calls.
  • Validates pgEdge Cloud capabilities for serving vector-based RAG workloads.
Read at source →
PostgreSQL News database

PostgreSQL pgtt v4.5 released with PG 19 support and concurrent index creation

The pgtt extension, which provides DB2 and Oracle-style global temporary tables for PostgreSQL, has updated to version 4.5. This maintenance release adds compatibility with PostgreSQL 19 and introduces support for CREATE INDEX CONCURRENTLY. The update also resolves several user-reported issues, including static variable declaration warnings and invalid OID errors during schema restoration from dumps.

  • Upgrade to pgtt v4.5 to gain native support for PostgreSQL 19.
  • Utilize the new CREATE INDEX CONCURRENTLY support to avoid locking issues.
  • Ensure dump restoration handles relation OIDs correctly to prevent errors.
  • Review static variable declarations to eliminate compiler warnings.
Read at source →
Planet PostgreSQL database

PostgreSQL: Excessive Table Counts Trigger OOM and CPU Hogging

Laurenz Albe reports that a high volume of tables in a PostgreSQL database caused out-of-memory crashes and CPU saturation. Investigation revealed that PostgreSQL itself was consuming excessive memory, rather than external software. The author suggests that managing table count is critical for stability under heavy load.

  • High table counts can cause PostgreSQL to consume excessive memory.
  • This may trigger Linux OOM killers or cause CPU saturation.
  • Disable memory overcommit as a first step in OOM investigations.
  • Monitor memory context dumps to confirm PostgreSQL as the source.
  • Review database schema design to reduce unnecessary table proliferation.
Read at source →
AWS What's New awsdatabase

RDS IAM DB Auth Now Scales with Instance Resources

Amazon RDS has updated IAM database authentication to dynamically scale connection rates based on available instance resources. This change allows enterprise workloads to handle high-volume connection patterns more effectively by leveraging the underlying compute capacity. Performance for new authentication requests is now directly tied to the instance's resource availability and workload characteristics.

  • IAM auth connection rates now scale with instance resources, supporting high-volume patterns.
  • Performance depends on available instance resources and current workload characteristics.
  • Reuse IAM user/role principals or authentication tokens to optimize performance.
  • Feature is generally available across all AWS Regions including GovCloud.
Read at source →
Planet PostgreSQL database

pgcopydb v0.18 released with 88 commits and major feature updates

Dimitri Fontaine has released pgcopydb v0.18, the project's largest update since August 2024, following a period of reduced developer availability. The tool accelerates PostgreSQL migrations by parallelizing data COPY operations and index creation across all tables simultaneously. It relies on logical replication for Change Data Capture to enable minimal-downtime moves and uses a local SQLite catalog to ensure interrupted jobs can resume seamlessly.

  • Parallelizes COPY and index build operations for significantly faster migrations.
  • Supports logical replication for minimal-downtime database moves.
  • SQLite-based state tracking allows safe resumption of interrupted jobs.
  • This is the most substantial release since v0.17 in August 2024.
Read at source →
Planet PostgreSQL database

PostgreSQL 18-19 Temporal DB Features: Keys, Periods, and Portions

PostgreSQL 18 introduced temporal keys with WITHOUT OVERLAPS constraints and PERIOD definitions to manage time-varying data. PostgreSQL 19 expands these capabilities by adding UPDATE and DELETE operations scoped to specific time portions. These features position Postgres as a more robust temporal database for historical data tracking.

  • Postgres 18 supports temporal keys with WITHOUT OVERLAPS and PERIOD definitions.
  • Postgres 19 adds portion-specific UPDATE and DELETE operations for temporal data.
  • These features enhance native support for time-varying data management.
  • No external temporal extensions required for basic temporal operations in newer versions.
Read at source →
Planet PostgreSQL database

PostgreSQL Logical Replication Gap: Sequence State Not Synced During Upgrades

While tools like pg_upgrade and pg_createsubscriber enable near-zero-downtime upgrades by converting replicas to logical subscribers, logical replication does not currently replicate sequence state. This creates a critical gap where sequence counters may diverge between source and target clusters after the switchover. The issue highlights a limitation in current upgrade workflows for PostgreSQL 19 clusters relying on logical replication.

  • Logical replication ignores sequence objects, causing counter mismatches post-upgrade
  • pg_createsubscriber converts physical replicas but leaves sequence state unsynced
  • Plan manual sequence reconciliation before cutover in zero-downtime upgrade plans
  • Test sequence generation after logical replication sync to avoid data integrity issues
Read at source →
↑