DEV Community

Discussion on: Supabase vs Neon: I measured both free Postgres tiers from India

Collapse
 
vladtkdev profile image
Vlad Tkachenko •

Since the GitHub Actions cron is there for the weekly ping anyway, the same job can cover the backup row in your table, which is also what Supabase's backup docs tell free projects to do: export regularly with supabase db dump and keep the copies off-site. Your IPv6 gotcha applies there too. Supabase lists GitHub Actions among the IPv4-only platforms, so the job needs the session pooler string. One trap when setting it up: supabase db dump on its own writes the schema and no rows. The guide does three files (roles, schema, and data with --data-only), and the data one is what you'd want after a dropped table.

Collapse
 
karthik_yk profile image
karthik •

Great addition — thanks. You're right on all three counts: one GitHub Actions cron can do double duty (keepalive ping + supabase db dump), GitHub runners are IPv4-only so the session pooler string is mandatory there too, and the schema-only default of db dump is exactly the trap that bites you the day you actually need the backup. The three-file split (roles / schema / --data-only) is the right pattern.

Folding this into the article's backup note. This is precisely the failure mode that matters on free tiers: no managed backups means the DIY backup had better actually contain the data.