© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•6mo ago•
32 replies
Timmy

Has the `supabase db pull` changed?

My workflow the last 6 months was to make changes on staging branch of the database, pull the changes localy so I can then push it to github. This allowed me to make quick changes for frontend developer and it was working perfectly until last week when the pull command started to act differently.
Now when I pull I usually get this or similar error:
error diffing schema: error running container: exit 1:
[select_097e65a]: Executing query failed: SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing
main worker has been destroyed
error diffing schema: error running container: exit 1:
[select_097e65a]: Executing query failed: SASL: SCRAM-SERVER-FINAL-MESSAGE: server signature is missing
main worker has been destroyed

I relink the project with the correct project ref and password and the error usually goes away for some time. But the pull is still not pulling the correct stuff, I made one RLS change and when I pull, I get 1000 line migration which repeats for infinite pull commands.

This happened now on three separate projects that all have branches enabled, I don't know if this is important.
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

supabase db pull
SupabaseSSupabase / help-and-questions
13mo ago
supabase db pull
SupabaseSSupabase / help-and-questions
3y ago
Supabase db pull, cast error
SupabaseSSupabase / help-and-questions
5mo ago
Trying db pull on supabase
SupabaseSSupabase / help-and-questions
12mo ago