Skip to content

Addition of pgmq extension not included in migration file made with supabase db diff #3379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SalmonMode opened this issue Apr 1, 2025 · 0 comments

Comments

@SalmonMode
Copy link

Describe the bug
After enabling the pgmq extension through the UI on my local environment, it does not include the extension in the migration I create right after using supabase db diff -f some_name

To Reproduce
Steps to reproduce the behavior:

  1. enable the pgmq extension through the UI
  2. Run supabase db diff
  3. No diff will be found

Expected behavior
It would include the extension in the migration

Screenshots
n/a

System information
Rerun the failing command with --create-ticket flag.

  • Ticket ID: no ticket ID was produced

  • Version of OS: Ubuntu 22.04

  • Version of CLI: 2.20.5

  • Version of Docker: 27.5.1

  • Versions of services:

     SERVICE IMAGE      │      LOCAL       │   LINKED
    

─────────────────────────┼──────────────────┼─────────────
supabase/postgres │ 15.8.1.054 │ 15.8.1.054
supabase/gotrue │ v2.170.0 │ v2.170.0
postgrest/postgrest │ v12.2.3 │ v12.2.3
supabase/realtime │ v2.34.43 │ -
supabase/storage-api │ v1.17.1 │ -
supabase/edge-runtime │ v1.67.4 │ -
supabase/studio │ 20250317-6955350 │ -
supabase/postgres-meta │ v0.87.1 │ -
supabase/logflare │ 1.12.0 │ -
supabase/supavisor │ 2.4.14 │ -

Additional context
If applicable, add any other context about the problem here.

  • Version of supabase-js 2.47.2
  • Version of Node.js: 20.18.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant