OffNet Newsroom

Daily topic roundup

Database Technology

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

Planet PostgreSQL database

PostgreSQL listen_addresses controls sockets, not access

The listen_addresses GUC determines which TCP interfaces PostgreSQL binds to, but it does not enforce authentication or authorization. Relying solely on this setting creates a false sense of security regarding network exposure. Access control must be handled separately through pg_hba.conf or external firewall rules.

  • listen_addresses only binds sockets; it does not filter connections.
  • Never use this GUC as a security boundary for network access.
  • Configure pg_hba.conf to enforce authentication and authorization.
  • Use OS-level firewalls to restrict traffic before it reaches PostgreSQL.
CHECKLISTSecure PostgreSQL Access ProperlyBind sockets via listen_addresses onlyEnforce auth with pg_hba.confRestrict traffic using OS firewalls

The PostGIS team released version 2025.2 of the PostGIS Tiger Geocoder extension, marking only the second release since it separated from the main PostGIS codebase. This update requires PostgreSQL 16 or higher and is compatible with any supported PostGIS version. Notably, the PostGIS 3.6 series will be the final release to include this extension, with version 3.7 shipping without it.

  • Requires PostgreSQL 16+; verify cluster versions before upgrading.
  • PostGIS 3.6 is the last core series including the geocoder.
  • PostGIS 3.7 will ship without the extension included.
  • Extension now lives in a dedicated OSGeo Gitea repo.
  • Versioning aligns with the US Census Tiger dataset year.
AWS Database Blog awsdatabase ↺ since 08-20

AWS blog: Diagnosing OOM and disk spilling in RDS for PostgreSQL

Amazon identifies out-of-memory events and excessive disk spilling as frequent production failures for RDS and Aurora PostgreSQL. The guidance explains PostgreSQL's memory allocation model and provides methods to pinpoint memory-heavy queries. It also outlines steps for diagnosing, preventing, and recovering from these critical incidents.

  • Focus on identifying queries that trigger excessive disk spilling to reduce I/O pressure.
  • Understand the specific memory allocation model to configure settings correctly.
  • Use provided diagnostic steps to quickly isolate the root cause of OOM events.
  • Apply preventive measures to avoid recurring memory exhaustion in production.
AWS Database Blog awsdatabase ↺ since 08-21

AWS blog details SQL Server to PostgreSQL full-text search migration pitfalls

Migrating full-text search engines from SQL Server to PostgreSQL often yields silent result discrepancies due to divergent text handling, linguistics, and accent processing. The AWS Database Blog outlines strategies to reproduce SQL Server search behavior on Aurora and RDS for PostgreSQL. Key alignment areas include managing collations, tokenization logic, accent-insensitive queries, and synonym dictionaries.

  • SQL Server and PostgreSQL tokenize and rank text differently, risking silent search regressions during migration.
  • Explicitly configure collations and accent-insensitive settings to match legacy SQL Server expectations.
  • Review tokenization rules and synonym lists to ensure linguistic consistency across engines.
  • Test search results rigorously on Aurora PostgreSQL and RDS to catch divergence early.

Fleet impact: This is meaningful database news. For teams running SQL Server and migrating to Aurora PostgreSQL or RDS, verify that full-text search result rankings and accent handling match production baselines. Audit collation settings and synonym dictionaries to prevent silent data retrieval failures after cutover.

Planet PostgreSQL database ↺ since 08-22

Postgres Insert Fails After Load Due to Sequence Drift

A successful data load using explicit IDs can leave Postgres sequences out of sync, causing subsequent application inserts to fail with unique constraint violations. This occurs because inserting explicit primary key values does not automatically advance the associated sequence to reflect the new maximum ID. The result is a database that appears intact but rejects valid writes until the sequence is corrected.

  • Explicit ID inserts do not update sequence metadata, causing future auto-generated inserts to collide.
  • Verify sequence alignment after bulk loads or data migrations that bypass serial columns.
  • Use setval() to manually sync sequences to the current max ID in the table.
  • Check for duplicate key errors immediately after ETL jobs complete, not just at load time.
HOW IT WORKSFixing Postgres Sequence Drift1Insert explicit IDs2Sequence stays low3Auto-insert collides4Run setval(max)5Writes succeed again
Planet PostgreSQL database ↺ since 08-21

PostgreSQL Shared Hash Tables for Parallel Aggregation Tested on Many-Core Instances

Andrei Lepikhov investigates whether shared hash tables can accelerate parallel aggregation in PostgreSQL by removing group lookups from under lock protection. The team developed a working patch set and benchmarked the approach on a Google Cloud many-core instance. The study evaluates if contention on LWLock is the primary bottleneck and assesses the performance trade-offs of this method.

  • Shared hash tables move group lookups out of lock contention, potentially boosting parallel aggregation speed.
  • Patch set tested on Google Cloud many-core instances to validate performance on high-core-count hardware.
  • Investigation challenges the notion that LWLock contention is the sole bottleneck in parallel aggregation.
  • Authors evaluate the specific performance costs and trade-offs of implementing shared hash tables.
CHECKLISTOptimizing Parallel AggregationMove group lookups out of lock contentionValidate performance on many-core instancesAssess trade-offs of shared hash tablesChallenge LWLock as sole bottleneck
Planet PostgreSQL database ↺ since 08-21

Bertrand Drouvot introduces pg_shmemviz for PostgreSQL shared memory debugging

Bertrand Drouvot has released pg_shmemviz, a new offline snapshot tool for visualizing PostgreSQL shared memory. It provides byte-level navigation and physical layout details that go beyond standard views like pg_buffercache, revealing C structure fields, padding, and pointer-referenced regions. This utility is designed for development and debugging to inspect the exact composition of main and dynamic shared memory segments.

  • Captures offline snapshots of main and dynamic shared memory segments for deep inspection.
  • Reveals physical layout, C structure fields, padding, and pointer-referenced raw bytes.
  • Complements existing views like pg_buffercache and pg_shmem_allocations with granular detail.
  • Useful for debugging memory allocation issues or understanding internal memory structures.
  • Follows the same architectural approach as the existing pg_walviz tool.
CHECKLISTDebugging with pg_shmemvizCapture offline snapshots of shared memory segmentsInspect C structure fields and padding detailsNavigate physical layout of raw byte regionsComplement pg_buffercache with granular insights
Percona Blog database ↺ since 08-21

PMM Vulnerability Allows Privileged ClickHouse Access via Grafana Source

Percona disclosed a high-severity security flaw in PMM versions 3.9.0 and earlier, where the Grafana data source configuration grants unauthorized privileged access to ClickHouse. This vulnerability allows attackers to bypass intended restrictions and interact directly with the underlying database engine. The advisory outlines the immediate remediation steps required to secure affected installations.

  • Audit all PMM instances running version 3.9.0 or lower immediately.
  • Check Grafana data source configurations for privilege escalation risks.
  • Apply Percona's recommended patches or configuration changes now.
  • Monitor ClickHouse logs for unauthorized access attempts during transition.
CHECKLISTSecure PMM Against ClickHouse ExploitAudit PMM instances running version 3.9 or lower immediatelyCheck Grafana data source configurations for privilege escalation…Apply Percona's recommended patches or configuration changes nowMonitor ClickHouse logs for unauthorized access attempts during…
↑