Default event triggers can be dropped

[steve-chavez]

Problem

These run:

drop function pgrst_ddl_watch cascade;
drop function pgrst_drop_watch cascade;

Despite them being owned by supabase_admin.

select evtname, evtowner::regrole, evtfoid::regproc from pg_event_trigger;

evtname	evtowner	evtfoid
issue_pg_graphql_access	supabase_admin	grant_pg_graphql_access
issue_graphql_placeholder	supabase_admin	set_graphql_placeholder
pgrst_ddl_watch	supabase_admin	pgrst_ddl_watch
pgrst_drop_watch	supabase_admin	pgrst_drop_watch
graphql_watch_ddl	supabase_admin	graphql.increment_schema_version
graphql_watch_drop	supabase_admin	graphql.increment_schema_version
issue_pg_cron_access	supabase_admin	grant_pg_cron_access
issue_pg_net_access	supabase_admin	grant_pg_net_access

select proname, proowner::regrole from pg_proc where prorettype = 'event_trigger'::regtype;

proname	proowner
event_trigger_in	supabase_admin
increment_schema_version	supabase_admin
pgrst_drop_watch	supabase_admin
pgrst_ddl_watch	supabase_admin
grant_pg_graphql_access	supabase_admin
set_graphql_placeholder	supabase_admin
grant_pg_net_access	supabase_admin
grant_pg_cron_access	supabase_admin

---

Note: previously on #1437 the ownerships were fixed

[coderabbitai]

🔗 Related PRs

#1987 - feat: add supabase_superuser role [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!