Update PGMQ Extension to Latest Version (1.5.0)

[jumski]

Update PGMQ Extension to Latest Version (1.5.0)

Is it an appropriate place to post about this request?

Describe the chore

Update the pgmq extension in Supabase-managed Postgres from version 1.4.4 to the latest version (1.5.0). The newer versions include:

1. A fix for high CPU usage in read_with_poll (v1.4.5), which is critical for running task queue workers efficiently.
2. Support for message headers (v1.5.0), enabling better handling of retries, errors, and other task metadata.

Additional context

The current version of pgmq in Supabase (1.4.4) is two versions behind Tembo’s latest release. Attempting to manually upgrade via Supabase CLI (v2.1.1) results in the following error:

ERROR:  22023: extension "pgmq" has no installation script nor update path for version "1.5.0"

This blocks adoption of important fixes and features necessary for implementing a reliable task queue worker. Would it be possible to share a timeline or plans for updating this extension?

[choxnox]

Is there any update here? The latest version of pgmq is now 1.5.1.

[adbl]

Please prioritize upgrading pgmq, at least to patch release 1.4.5 which fixes pgmq/pgmq#343

Without this fix, any poll duration <1000ms results in 100% CPU. As mentioned in the issue description, this is needed for worker/task patterns.

[adbl]

@jumski were you able to upgrade to 1.4.5 manually?

[jumski]

Hey! @adbl

I'm using pgmq in my Supabase-dedicated workflow engine pgflow and i ship a backported read_with_poll to include the fixes from the issue you linked (but with small changes to exclude the headers for now) - https://github.com/pgflow-dev/pgflow/blob/main/pkgs/core/schemas/0080_function_read_with_poll.sql

I haven't tried to pull all the changes but it should be relatively simple, as pgmq is pure SQL really. If you want you can run the migrations in order from the source https://github.com/pgmq/pgmq/tree/main/pgmq-extension/sql but it will probably break future updates when Supabase will get pgmq to newest version

[adbl]

Awesome, thanks! We will live with 1000ms poll for now as I don't want upgrade headache later.

[jumski]

You can do what I did in pgflow and just back port read_with_poll into a new schema. You can copy the code I linked as it is compatible with 1.4.4 but includes the interval fix. This way when supabase fixes it you will not have conflicts and can only switch back to pgmq.read_with _poll