© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•6mo ago•
3 replies
sheisty6

Branching Drift Caused by Storage Triggers

Hello,

I am trying to create a persistent staging branch that is in sync with production. The process I used was:
1. Create branch
dev
dev
off of
production
production

2. Run a data dump and run the dump script in
dev
dev
SQL editor
3. Run a query in
production
production
to get all triggers so that I can manually copy them over (they don't seem to come over thru the dump)

I'm running into issues copying over some triggers on the storage table, with commands like:
CREATE TRIGGER prefixes_delete_hierarchy AFTER DELETE ON storage.prefixes FOR EACH ROW EXECUTE FUNCTION storage.delete_prefix_hierarchy_trigger();
CREATE TRIGGER prefixes_delete_hierarchy AFTER DELETE ON storage.prefixes FOR EACH ROW EXECUTE FUNCTION storage.delete_prefix_hierarchy_trigger();


Failing with error:
ERROR:  42P01: relation "storage.prefixes" does not exist
ERROR:  42P01: relation "storage.prefixes" does not exist


I've attached a screenshot of the
production
production
storage triggers. I do not remember creating these, were they a byproduct of some setting? Can I safely delete them in
production
production
, or copy them over to
develop
develop
?

Thanks!
Screenshot_2025-09-02_at_3.14.34_PM.png
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

Atomic triggers on storage
SupabaseSSupabase / help-and-questions
4mo ago
Regarding branching
SupabaseSSupabase / help-and-questions
4mo ago
Supabase Branching
SupabaseSSupabase / help-and-questions
4mo ago
supabase branching
SupabaseSSupabase / help-and-questions
4mo ago