bugfix

pgflow 0.7.2: Fix Missing Realtime Broadcasts for Step Events

Nov 4, 2025 - 1 min read

Featured

pgflow 0.7.2 fixes missing realtime broadcasts that prevented clients from receiving step:started and step:completed events. PostgreSQL’s query optimizer was eliminating CTEs containing realtime.send() calls because they weren’t referenced by subsequent operations.

What’s Fixed

step:started events now broadcast when steps begin executing
step:completed events now broadcast for empty map steps
step:completed events now broadcast for cascade completions
Client applySnapshot() methods added for proper initial state hydration without event emission

Additional Changes

Enhanced test coverage for realtime event lifecycles
Documentation updates for abort signal support and empty map step behavior

Upgrading

Questions or issues? Join our Discord community or open an issue on GitHub.

pgflow 0.7.1: Fix pgmq 1.5.1 Version Conflict on New Supabase Projects

Oct 30, 2025 - 1 min read

Wojciech Majewski (@jumski)

Creator and Maintainer

Featured

pgflow 0.7.1 fixes installation failures on fresh Supabase projects caused by pgmq version mismatch.

The Bug

Installing pgflow on new Supabase projects failed with:

ERROR: extension "pgmq" has no installation script nor update path for version "1.4.4" (SQLSTATE 22023)
At statement: 2
CREATE EXTENSION IF NOT EXISTS "pgmq" WITH SCHEMA "pgmq" VERSION "1.4.4"

Why It Happened

Supabase upgraded to pgmq 1.5.1 in Postgres 17.6.1.016+ (supabase/postgres#1668). pgflow’s initial migration was pinned to version 1.4.4, which no longer exists in new Supabase instances.

The Fix

Removed the version constraint from pgmq extension creation. pgflow now uses whatever pgmq version Supabase provides (1.4.4, 1.5.1, or newer).

CREATE EXTENSION IF NOT EXISTS "pgmq" WITH SCHEMA "pgmq" VERSION "1.4.4";
CREATE EXTENSION IF NOT EXISTS "pgmq" WITH SCHEMA "pgmq";

Credits

Thanks to @kallebysantos for reporting this issue!