[2.62.5] DatabaseError

[mrtnbroder]

Bug report

Recent supabase 2.62.5 update breaks with a DatabaseError

> supabase db reset

Resetting local database...
Recreating database...
WARNING (42602): invalid configuration parameter name "supautils.disable_program", removing it
Initialising schema...
Seeding globals from roles.sql...
Applying migration 20251020105412_first-draft.sql...
WARN: no files matched pattern: supabase/seed.sql
Restarting containers...
Error status 500: {"statusCode":"500","code":"DatabaseError","error":"DatabaseError","message":"select * from ((select \"id\", \"name\", \"public\", \"owner\", \"created_at\", \"updated_at\", \"file_size_limit\", \"allowed_mime_types\", \"type\" from \"buckets\") union all (select \"id\", \"id\" as \"name\", null as \"public\", null as \"owner\", \"created_at\", \"updated_at\", null as \"file_size_limit\", null as \"allowed_mime_types\", \"type\" from \"buckets_analytics\")) as \"all_buckets\" - UNION types text and uuid cannot be matched"}

• [x] I confirm this is a bug with Supabase, not with my own application.
• [x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Latest supabase update now throws an DatabaseError

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. brew install supabase
2. supabase init
3. supbase db reset

Expected behavior

supabase should not throw a databaseerror

Screenshots

If applicable, add screenshots to help explain your problem.

System information

• OS: macOS, Docker
• Version of supabase-js: v2.84.0
• Version of Node.js: v24.11.0

[dawson-homekeepr]

In the meantime, the issue resolves for me by rolling back the supabase npm package to version 2.58.5.

[rickyhonline]

same issue

[otizhi]

Same problem

[Hallidayo]

Transferred over from the supabase/supabase repo

[lorandfazakas]

Same issue here. Still present with 2.62.10

[lorandfazakas]

@mrtnbroder wiping the local docker containers and images and restarting the supabase environment from scratch fixed the issue for me.

[roccoe]

Wipinig the container worked for me and my colleagues too. Just doing supabase stop and recreating with supabase start did the trick for me.

[SpencerGreene]

supabase stop + start did not work for me unfortunately. downgrade did.

[sboagy]

Me too. This is really irritating.