v0.2.1 — Upgrade Infrastructure and Documentation

Full technical details: v0.2.1.md-full.md

Status: ✅ Released | Scope: Small (~1–2 weeks)

Safe in-place upgrades and a significantly expanded documentation set covering operations, configuration, and common patterns.

What problem does this solve?

Early adopters of pg_trickle needed a safe path to upgrade from one version to the next without dropping and recreating their stream tables. They also needed comprehensive documentation to go beyond the basics. v0.2.1 delivers both.

Extension Upgrade Scripts

PostgreSQL extensions can be upgraded in place using ALTER EXTENSION pg_trickle UPDATE TO '0.2.1'. This requires carefully crafted migration SQL scripts that bring the catalog schema from the old version to the new one without data loss.

v0.2.1 ships the first complete upgrade infrastructure — SQL migration scripts for each version transition, a check-version-sync validation command, and a tested upgrade path from v0.2.0 to v0.2.1.

In plain terms: you can now upgrade pg_trickle versions with a single SQL command and your stream tables, their data, and their schedules are all preserved.

Documentation Expansion: 20+ New Pages

The documentation set more than doubled in size, adding over 20 pages covering:

  • Getting Started — step-by-step guide from installation to first stream table
  • Configuration — every GUC (configuration variable) with its purpose, default, and recommended tuning
  • Patterns — common use cases and the idiomatic pg_trickle approach for each
  • Troubleshooting — the most common problems and how to diagnose them
  • FAQ — answers to questions asked by early users

Scope

v0.2.1 is an infrastructure and documentation release. No new query patterns or operational capabilities were added, but the extension is now significantly easier to adopt, maintain, and upgrade.