HypoPG 1.4.4 fixes hypothetical index bugs, adds PostgreSQL 19 compatibility

HypoPG 1.4.4, the PostgreSQL extension for creating hypothetical indexes without physical storage overhead, has been released with a focused set of bug fixes and forward-compatibility updates. The release addresses critical correctness and stability issues including hypothetical index name generation for Oid values at or above 2^31, memory leakage in WITH clause option handling, and protection of the hypothetical Oid range from collision with user-created objects. It also corrects catalog column output in the hypopg() function and prevents failed EXPLAIN operations from corrupting subsequent query execution states.

The release adds compatibility fixes for PostgreSQL 19, the next major version currently in release candidate stage. HypoPG remains compatible with PostgreSQL 9.2 and above, maintaining its long support window for database administrators who use hypothetical indexes to evaluate query optimization strategies without committing storage resources.

Bug fixes and PostgreSQL 19 compatibility in HypoPG 1.4.4

• Oid overflow handling: Fixes hypothetical index name generation for Oid values greater than or equal to 2^31, preventing name collisions and potential catalog corruption on large or long-running deployments.
• Memory management: Eliminates a memory leak in WITH clause option processing, reducing resource consumption during repeated hypothetical index operations in complex queries.
• Column validation: Adds enforcement of maximum column limits for included columns in hypothetical indexes, matching PostgreSQL's physical index constraints and preventing invalid index definitions.
• Cache invalidation: Implements targeted invalidation of hypothetical indexes when dependent objects (relations, functions, access methods, operator classes, types) receive invalidation messages, with fallback to broader invalidation for other object types.
• Query isolation: Prevents failed EXPLAIN commands from affecting subsequent queries, correcting a state contamination bug that could silently alter execution plans or error behavior in later operations.

Why it matters

Database administrators and query optimization specialists who rely on HypoPG to evaluate index strategies without storage overhead gain improved reliability on large catalogs and long-running sessions. The PostgreSQL 19 compatibility work ensures this tooling remains viable through the upcoming major version transition, reducing upgrade friction for performance engineering workflows.