PostgreSQL consultant Christophe Pettus has published a detailed analysis of recovery_end_command, the only GUC hook that fires exactly once when a standby is promoted or a restore completes. While the command runs, the server occupies an undocumented intermediate state: timeline files are written, the signal file is deleted, and pg_is_in_recovery() still returns true, yet writes are rejected. A command that exceeds pg_ctl promote's 60-second default timeout causes the promote command to report failure even though promotion proceeds. Worse, a typo or bad placeholder in the command can FATAL-crash the server after all WAL is replayed, leaving it on a new timeline with cleanup skipped and the broken command still in postgresql.conf. Pettus recommends leaving the parameter empty.

The PostgreSQL YUM and ZYPP repository websites have launched new Software sections listing more than 70 packages across categories including backup, high availability, connection pooling, monitoring, and migration. Each package page includes descriptions, exact dnf or zypper install commands, and a live-generated table showing which OS versions, architectures, and PostgreSQL versions currently support it. Previously, only extensions had documentation pages, leaving tools like pgBackRest, Patroni, and PgBouncer difficult to discover without knowing their exact package names.

PostgreSQL 19 has reached its first release candidate stage. The upcoming major release focuses on practical improvements in three areas: database maintenance operations, query planner behavior, and replication reliability. Database administrators and application developers should begin testing against this RC.

Awide Labs has open-sourced Awide Polar, its fork of PolarDB for PostgreSQL built on PostgreSQL 17. The project separates compute and storage so read replicas share underlying data files without full copies, while a primary handles writes. The release includes three components: the database engine with WAL pipelining and increased lock partitioning, an enhanced PolarFS storage layer with lock-free I/O queues, and Polar Proxy for LSN-aware read/write splitting. The company reports over 150,000 TPS in pgbench read/write tests and 7-11x filesystem IOPS improvements over upstream PolarFS.

pgsql_tweaks, a collection of utility functions and views for PostgreSQL, has released version 1.1.0. The update adds pg_index_bloat, a new view for identifying bloated indexes. The extension is available via Codeberg, PGXN, and PostgreSQL RPM packages.

Database consultant Christophe Pettus traces how PostgreSQL's random_page_cost parameter actually works in the query planner, correcting widespread misconceptions. The parameter has never measured raw random read speed; it multiplies that cost by cache miss probability. The 4.0 default, set in 2000 for spinning disks, was explained in documentation from 2012-2025 as a 40:1 hardware ratio discounted by 90% cache hits. That explanation and a 2020 SSD recommendation of 1.1 were both removed in October 2025. Recent benchmarks by Tomas Vondra found actual ratios of 20-63 on modern storage, suggesting 4.0 may be too low rather than too high, though methodology disputes remain unresolved and the default stays 4.0 in version 19 beta 4.

pg_hint_plan 1.9.0 has been released with compatibility for PostgreSQL 19, the upcoming major version of the database. The release introduces support for path generation strategies (PGS), a new mechanism for influencing how PostgreSQL builds query execution plans. The development team also issued maintenance updates for supported PostgreSQL versions back to 14, with 1.4.5 being the final release for PostgreSQL 14.

pg_utl_smtp 2.0.0 brings asynchronous email delivery to PostgreSQL, a capability not present in Oracle's original UTL_SMTP package. The release also adds SSL/TLS connections, fixes duplicate EHLO commands, and raises errors on SMTP failures during any protocol stage. The extension lets triggers and stored procedures send email directly, enabling data-driven alerts without application-layer involvement.

pgBackRest 2.60.0 changes the default behavior for page checksum validation during restore: invalid checksums now cause the restore to halt, leaving the cluster incomplete until rerun. Administrators can revert to warnings with checksum-page-error=n. The release also adds Google Cloud Storage Workload Identity Federation for authentication without service account keys, and implements multi-file/range prefetching from object stores to accelerate reads. OpenSSL 4 and illumos builds are now supported.

HexaCluster has released credcheck 6.0, a major update to the PostgreSQL credential-checking extension. The release adds PgBouncer compatibility for two previously unsupported features, introduces session logging comparable to Unix last/wtmp, and provides a new function to test passwords against policy without modifying roles. It also patches a privilege escalation via self-ALTER ROLE, memory leaks, and a heap overflow. Administrators must restart PostgreSQL to load the updated library.

A technical deep dive explains how mismatched keyword lists between pg_dump and the PostgreSQL server can cause silent data integrity issues during upgrades. When a column name becomes a reserved keyword in a newer version, failing to use the --quote-all-identifiers switch can result in broken indexes, invalid check constraints, and malfunctioning row-level security policies. The feature works via a combination of a command-line switch for the client and a GUC for the server to ensure all identifiers are quoted consistently.

A new benchmark from StackGres compares the performance of open-source Citus against PlanetScale's Neki sharded PostgreSQL. By introducing scalable Query Routers to remove the single-coordinator bottleneck, Citus matched Neki's 10M QPS throughput while utilizing only 48% of the data nodes and significantly fewer vCPUs. The test was conducted on AWS Graviton4 instances using a read-only workload.

PostgreSQL 18 will feature a significant update to how the database handles Non-Uniform Memory Access (NUMA) architectures via libnuma. The changes, contributed by Tomas Vondra, allow the system to interleave shared resources like shared buffers and the ProcArray while ensuring backend-local allocations remain on the local NUMA node. This approach aims to reduce memory access penalties and lock contention on large-scale hardware.

The 2026 Ruby on Rails Community Survey results reveal that 84% of surveyed developers use PostgreSQL in production environments. This significantly outpaces MySQL, which is used by 23% of respondents. The data highlights PostgreSQL's growing dominance in the relational database market compared to legacy systems like Oracle and Microsoft SQL Server.

The pgAdmin project has overhauled its build process by addressing vulnerabilities in its dependency management. By moving from mutable tags to immutable releases and implementing SHA-256 lock files, the project now ensures that the libraries included in Windows and macOS installers are exactly what the developers intended, improving both security and build reproducibility.

An analysis of the primary_slot_name parameter reveals how replication slots impact WAL retention and vacuum processes. If a standby disconnects while holding a slot, the upstream server continues to retain WAL files and prevents VACUUM from cleaning up dead rows. This can lead to disk exhaustion and significant table bloat if not managed via max_slot_wal_keep_size or idle_replication_slot_timeout.

As part of the PostgreSQL 19 CommitFest, new features aim to improve database administration and maintenance. The update introduces the REPACK command, which includes a CONCURRENTLY option to rebuild tables without blocking writes, and a new scoring mechanism for autovacuum to process relations based on configurable weights.

ClickHouse has announced the release of version v26.8.28.14-lts. This release is part of the long-term support series. The exact changes and updates in this version are not specified in the release notes.

ClickHouse has announced the release of version 26.7.31.12-stable. This release is part of the stable branch of the columnar database management system. The exact changes and updates in this version are not specified in the release notes.

The PostgreSQL Global Development Group has released the first release candidate (RC 1) of PostgreSQL 19. This version includes bug fixes applied since Beta 4 and serves as a precursor to the final release. A second release candidate is expected on November 12, 2026, followed by the general availability of PostgreSQL 19 on November 19, 2026.

The Perseid 0.1.0 release introduces a set of utilities designed to version PostgreSQL database schemas. As the successor to Pyrseas, the tool includes dbtoyaml and yamltodb to extract schemas into YAML format and apply SQL changes to match a target specification. This initial version requires PostgreSQL 17 or higher.

The psqlODBC team has released version 18.00.0005 to address CVE-2026-109448, a medium-severity vulnerability. The flaw involved heap memory corruption when an application bound more than 32,768 parameters due to the use of a signed 16-bit field. This release also fixes bugs related to type name truncation and bytea parameter handling in Microsoft's OLE DB Provider.

The PgBouncer 1.26.1 release addresses three security vulnerabilities. These include a critical authentication bypass affecting SCRAM users and two Denial of Service (DoS) flaws caused by infinite loops.

The beta release of pglifecycle 2.0 introduces a complete rewrite of the tool in Rust. This schema management utility allows users to manage PostgreSQL objects like tables, views, and functions as individual YAML files in version control. It supports pulling existing databases into projects, generating DDL for reconciliation, and integrating with CI via a GitHub Action.

The latest release of Qdrant Vector Database, version 1.19.0, introduces several new features, including TurboQuant 4-bit as a datatype of primary vector storage and a global quota API. It also includes numerous improvements and bug fixes, enhancing performance, memory usage, and overall functionality. This update affects users and developers working with vector databases and related applications.

The PostgreSQL JDBC team has issued a security release, version 42.7.14. This update addresses two specific vulnerabilities identified as CVE-2026-107314 and CVE-2026-107315, which are also tracked via GitHub Security Advisories.

PGX Inc. has released version 1.0 of pgx-bm25, an extension that implements Okapi BM25 ranking directly within PostgreSQL. Supporting versions 17 and 18, the extension functions as a native index, utilizing PostgreSQL's existing WAL logging, crash recovery, and replication mechanisms. It eliminates the need for external search engines by integrating text analysis via Snowball dictionaries and optimizing top-N queries with the block-max WAND algorithm.

The pg_plan_filter 1.0.0 module has been released to help administrators protect production databases from expensive queries. It works by testing statements against configured cost criteria before they are executed. The module is compatible with PostgreSQL versions 14 through 18.

The Qdrant vector database has released version 1.19.2, focusing on performance improvements and stability. Key updates include faster sparse vector upserts, better thread utilization during HNSW builds, and expanded object storage support for snapshots. The release also addresses several data consistency bugs and security hardening for internal gRPC calls.

The Apache Iceberg 1.12.0 release brings significant updates to the table format specification and ecosystem integrations. Key changes include support for writing Parquet and Avro manifests in the V4 spec, the removal of Spark 3.4 support, and various improvements for Flink and Kafka Connect. The release also introduces new security model documentation and technical refinements to core IO operations.

The DuckDB analytical engine has released version 1.5.6, a maintenance update focused on bug fixes. The release resolves issues related to Top-N window elimination, Parquet metadata handling, and memory management during scans. It also includes updates to several extensions including httpfs, vortex, and iceberg.

Valkey has released the 9.2.0-rc1 release candidate, introducing major architectural and functional updates. Key additions include opt-in forkless RDB snapshots, a new radix-tree-backed Path Hash data type, and a more robust ACL system with reusable roles. The release also focuses on performance, featuring B+ tree backing for large sorted sets and improved memory management.