PostgreSQL 18 introduces the extension_control_path GUC, allowing extensions to be installed in arbitrary directories rather than the system-wide extension directory. This change decouples extension location from the core installation structure, enabling more flexible deployment strategies. The update removes the previous hard constraint that forced all extensions into a fixed system path.
Extensions can now reside in custom directories via extension_control_path
Ends the requirement to install extensions into the system directory
Shaun Thomas highlights a significant but overlooked feature in Postgres 19: enhanced control over manual CHECKPOINT operations. Previously, issuing a manual checkpoint was a blunt instrument that triggered an immediate, uncontrolled flush of pending writes to disk. The new release introduces finer-grained mechanisms to manage this process, addressing storage I/O spikes that can occur when background checkpoints or manual invocations overwhelm the system.
Manual CHECKPOINT behavior is enhanced in Postgres 19 for better I/O management.
DBAs can now invoke checkpoints with more predictable resource impact.
Review Postgres 19 release notes for specific syntax changes to checkpoint control.
Tuning storage performance should account for these new checkpoint options.
Fleet impact: For fleets running heavy write workloads, Postgres 19's improved manual checkpoint control allows DBAs to flush data without causing sudden I/O storms that could impact latency. Ensure your operational scripts for maintenance windows are updated to leverage these new parameters if available, and monitor storage throughput during manual checkpoints to validate the reduced impact.
Jimmy Angelakos presents findings from POSETTE and PG DATA 2026 regarding PostgreSQL's LISTEN and NOTIFY mechanism. He details a production incident where asynchronous inter-process communication via NOTIFY created a significant performance bottleneck. The talk highlights how this feature can quietly degrade database throughput under high-load conditions.
PostgreSQL LISTEN/NOTIFY can cause severe performance bottlenecks in high-throughput scenarios.
Review current usage of NOTIFY for async IPC to identify potential hidden latency sources.
Monitor database performance metrics closely when scaling asynchronous message passing.
Consider alternative communication patterns if NOTIFY becomes a production constraint.
DoltHub has released version 2.0 of its open-source version-controlled SQL database, introducing automatic storage optimization features like garbage collection and compression. This update also enhances support for large and vector data types to handle more complex data workloads. The release aims to reduce storage overhead while improving efficiency for versioned database operations.
Automatic garbage collection and compression reduce storage overhead without manual intervention.
Improved support for large and vector data types expands use cases for AI and media workloads.
Version control remains core to Dolt, enabling SQL-level branching and merging capabilities.
Storage optimization helps manage growth in versioned databases over time.
Release targets practitioners managing data lineage and collaboration in SQL environments.
A recent technical analysis shares operational insights gained from deploying SQLite at scale. The author details specific configuration adjustments and usage patterns that improve stability and performance in real-world scenarios. These findings highlight how SQLite can be managed effectively beyond simple embedded use cases.
SQLite requires specific WAL mode and busy timeout settings for concurrency.
Connection pooling strategies differ significantly from traditional RDBMS.
Monitoring file descriptors and disk I/O is critical for longevity.
Schema migrations need careful handling to avoid locking issues.
Jimmy Angelakos has released the recording of a LinkedIn Live session focused on correcting common SQL anti-patterns in PostgreSQL. Based on Chapter 2 of his Manning book, the session demonstrates how specific mistakes lead to incorrect results or hidden performance degradation. It pairs concise explanations with live terminal demos, showing practical refactors that restore correct logic and enable efficient index usage.
Recording covers anti-patterns from 'PostgreSQL Mistakes and How to Avoid Them' book.
Live demos show exact query failures and their practical refactors.
Focuses on fixing incorrect results and unlocking proper index usage.
Hybrid format combines short explanations with real-world terminal examples.
Amazon RDS now offers PostgreSQL 19 Beta 2 in the Database Preview Environment for evaluation. Key updates include parallel autovacuum with configurable worker limits to prevent maintenance bottlenecks on large tables. The release also introduces the REPACK CONCURRENTLY command for online table rebuilding and native SQL Property Graph Queries (SQL/PGQ) for relationship traversals.
Test parallel autovacuum tuning to ensure large database maintenance does not block production workloads.
Evaluate REPACK CONCURRENTLY as a native replacement for third-party extensions like pg_repack.
Assess SQL/PGQ adoption to simplify graph traversal logic directly within standard SQL queries.
Use the RDS Preview Environment to validate compatibility before general availability.
Fleet impact: Enable the preview environment to stress-test parallel autovacuum configurations, which will significantly reduce I/O contention during peak maintenance windows on large Aurora PostgreSQL or RDS instances. Verify application compatibility with SQL/PGQ if your stack relies on graph-like data models, as this may allow you to remove external graph processing layers.
