Database Technology

PL/Ruby 3349 is a procedural language handler that embeds the MRI Ruby interpreter directly into the PostgreSQL backend. It allows developers to write functions, triggers, and procedures in Ruby 3.x, supporting scalar and array types across PostgreSQL versions 11 through 18. This extension mirrors the feature set of PL/PHP while providing access to Ruby's standard library within the database engine.

• Native MRI Ruby embedding enables Ruby 3.x usage for DB functions and triggers.
• Supports PostgreSQL 11-18 via a standard CREATE EXTENSION installation.
• Covers plain functions, set-returning functions, and transaction-controlled procedures.
• Provides Ruby expressiveness with full access to PostgreSQL native capabilities.

PostgreSQL’s extensive catalog of built-in functions still leaves gaps in areas like generating random dates or retrieving exact role definitions. Postgres 19 aims to alleviate these annoyances by introducing new quality-of-life enhancements to fill these functional voids. The update focuses on reducing the need for complex expressions or external GUI tools for common administrative and testing tasks.

• Postgres 19 addresses missing built-in functions that currently require complex workarounds.
• New features simplify generating test data, such as random dates within specific years.
• Administrative tasks like retrieving exact role or tablespace definitions will be streamlined.
• Reduces reliance on external tools like pgAdmin for basic schema introspection.

Percona’s investigation into memory allocators revealed anomalous memory consumption patterns specific to stored procedures in Percona Server for MySQL. The findings suggest that routine performance benchmarking can uncover hidden resource behaviors that are not immediately obvious during standard setup or operation. This analysis provides a detailed explanation of these effects to help practitioners understand potential overhead.

• Stored procedures may consume more memory than expected, even when using standard allocators.
• Benchmarking for memory performance can reveal hidden resource consumption issues.
• Percona Server for MySQL users should review procedure memory footprints in their environments.
• Unexpected memory effects highlight the need for deeper performance investigation beyond basic checks.

PostgreSQL 19 introduces SQL Property Graph Queries (SQL/PGQ) via a patch committed by Peter Eisentraut in March 2026. The update implements the ISO/IEC 9075-16:2023 standard, adding the GRAPH_TABLE function for pattern matching and DDL commands for property graphs. New system catalogs and information schema views support this native graph capability.

• PostgreSQL 19 now supports native graph queries via the ISO/IEC 9075-16:2023 standard.
• GRAPH_TABLE function enables SQL-based graph pattern matching without external tools.
• New DDL commands CREATE/ALTER/DROP PROPERTY GRAPH simplify graph schema management.
• System catalogs and information schema views extend introspection for graph objects.

PostgreSQL 18 introduces a Grand Unified Configuration (GUC) named extension_control_path, allowing extension control and SQL files to reside outside the server's core directories. This change enables packaging extensions as independent OCI container images that can be mounted at runtime, eliminating the need to rebuild the main PostgreSQL server image for updates. This approach supports versioning extensions like pgvector separately from the database engine, though the benefit varies depending on the extension's complexity and dependencies.

• New GUC extension_control_path allows external storage of extension files.
• Enables independent OCI container packaging for extensions without server rebuilds.
• Simplifies upgrading specific extensions like pgvector while keeping the base image stable.
• Decoupling is most effective for self-contained extensions with minimal system dependencies.

Pavlo Golub announces vip-manager v5, a critical update for managing Virtual IPs in PostgreSQL high availability setups. This release introduces breaking changes that alter cluster behavior during failover events, making it risky to perform silent upgrades. The tool continues to watch distributed configuration stores like Patroni or etcd to ensure the VIP attaches only to the current leader node.

• Do not blindly run apt upgrade; new release logic changes failover behavior.
• Review breaking changes to avoid unexpected downtime during 03:00 incidents.
• Verify VIP attachment logic works correctly with your specific DCS (Patroni, etcd, etc.).
• Update runbooks to reflect new vip-manager v5 operational constraints.