Viewing on GitHub? The roadmap lives in ROADMAP.md. This stub is served by the pg_trickle docs site — the include below renders there.

pg_trickle roadmap

This page tracks current release work and longer-term direction. See CHANGELOG.md for shipped releases and the linked release plans for details.

Current work

pg_trickle keeps PostgreSQL query results fresh through incremental view maintenance. v0.105.3 fixed the known DVM issue and made qualification a release requirement.

VersionFocusStatus
v0.106.0Verify package support, pending-data upgrades, platform tiers, and database resource budgets with executed evidence.Released
v0.107.0Back support claims and operator procedures with runtime tests.In progress
v0.108.0Make at most two internal changes for reproduced defects or measured performance costs. Skip this release if the evidence does not justify a change.Conditional

Release constraints

  • Preserve committed changes and transaction durability.
  • Use differential refresh wherever supported. Keep whole-query FULL as a visible fallback of last resort.
  • Add no SQL families, public contract versions, capture backends, integrations, or autonomous controller actions in this phase.

v1.0 status

There is no v1.0 target date. Qualification, the 72-hour mixed-workload soak, the longevity environment, and the release-candidate series remain deferred. The v1.0 plan defines the stability contract, including correctness, upgrade safety, stable public interfaces, and qualified packages.

Beyond v1.0

These plans are not v1.0 requirements. See each release plan for scope.

VersionDirectionStatus
v1.1.0PostgreSQL 17 support, SEARCH and CYCLE, and an auto_explain hook.Planned
v1.2.0PGlite proof of concept and pg_partman integration.Planned
v1.3.0Extract pg_trickle_core.Planned
v1.4.0PGlite WASM extension.Planned
v1.5.0Reactive PGlite integration.Planned
v1.6.0Opt-in query acceleration using sufficiently fresh stream tables.Planned
v1.7.0Optional external workers and CDC consumers.Optional
v1.8.0Optional distributed computation and Kubernetes operator.Optional
v1.9.0Speculative federation and object-storage state, only if users ask for it.Conditional