S
Supabase9mo ago
jumski

PGMQ versioning in Supabase - question

Tembo recently released PGMQ 1.5.0, which adds message headers - a super useful feature for metadata like retry info, task handler names, and error details (similar to HTTP headers). However, the PGMQ version shipped with Supabase is still at 1.4.4 (two versions behind). This also means we’re missing the 1.4.5 fix for high CPU usage in read_with_poll. I tried upgrading locally using the Supabase CLI (v2.1.1) but hit this error:
ERROR: 22023: extension "pgmq" has no installation script nor update path for version "1.5.0"
ERROR: 22023: extension "pgmq" has no installation script nor update path for version "1.5.0"
\dx pgmq confirms the current version is 1.4.4. Questions: 1. Is the PGMQ version hardcoded in Supabase, meaning we have to wait for Supabase to upgrade it? 2. If not, how can we upgrade it manually in a Supabase-managed environment? 3. If it is locked, is there any way to apply the SQL changes manually for a partial upgrade (assuming only SQL changes are involved)? For reference, here’s the PR introducing headers: https://github.com/tembo-io/pgmq/pull/338 Any guidance would be greatly appreciated!
4 Replies
garyaustin
garyaustin9mo ago
Normally extensions are set for hosted (and probably local dev) and Supabase releases updates when they feel they are safe. https://github.com/supabase/postgres/blob/2043276484dc9c7e17115410ec0d0262d0e5d0f4/nix/ext/pgmq.nix#L4
jumski
jumskiOP9mo ago
I've looked in the wrong repo, thank you Gary! Any idea if it would be possible to escalate to speed up the upgrade? The read_with_poll fix is a must-have to be honest, im hitting the high CPU utilization in my queue worker. I can live without headers tho but they would be massively useful for my project.
silentworks
silentworks9mo ago
Supabase don't generally speed up or upgrade user instance on individual basis. You'll just have to wait until they have tested the latest versions and release them. You can always open an issue on the GitHub repo Gary linked to.
jumski
jumskiOP9mo ago
Understood. Will probably open ticket. In meanwhile I will just use the new implementation for read_with_poll as 1.4.5 seems to be an SQL-only change (https://github.com/tembo-io/pgmq/compare/v1.4.4...v1.4.5). I really appreciate your support guys ❤️

Did you find this page helpful?