Skip to content
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

supabase db pull not retrieving function definition of functions on remote DB #2266

Open
eRuaro opened this issue May 11, 2024 · 1 comment

Comments

@eRuaro
Copy link

eRuaro commented May 11, 2024

Describe the bug
I upgraded my postgres version on cloud supabase and wanted to have my local setup match the cloud setup.

I removed my /supabase folder and ran the supabase init process again and linked my project but this time I'm getting that a function does not exist on my local supabase setup when running supabase db reset after running supabase db pull

To Reproduce
Steps to reproduce the behavior:

  1. Initialize supabase project with psotgres version >= '15.1.1.44'
  2. Have the vector extension on cloud supabase
  3. Run supabase init
  4. Run supabase db pull
  5. Run supabase db reset
  6. See error
Error: ERROR: function public.hnswhandler(internal) does not exist (SQLSTATE 42883)
At statement 176: GRANT ALL ON FUNCTION "public"."hnswhandler"("internal") TO "postgres"

Expected behavior
I expected that my local dev supabase will run just fine but it's not.

Upon running SELECT pg_get_functiondef(to_regprocedure('public.hnswhandler(internal)')); via PSQL on my local dev setup, it says that the function does not exist. However running the same on the hosted supabase DB will return the function definition.

System information

  • Version of OS: Ubuntu 20.04
  • Version of CLI: 1.167.4
  • Version of Docker: 24.0.6
  • Versions of services:
    image

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

  • Version of Node.js: V19.6.0
@eRuaro
Copy link
Author

eRuaro commented May 15, 2024

I believe this is now related to this recent issue I filed: #2288

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