---
title: "Comment by Vlad Tkachenko on \"Automate Supabase Database Backups Using GitHub Actions\" | Hashnode"
description: "Useful post, and the IPv6 diagnosis is the part most of these guides miss. One thing to check in Step 1 though: the string you landed on uses the pooler's user"
url: "https://hashnode.com/posts/automate-supabase-database-backups-using-github-actions/6966fd0107e1f88430202be6/comment/6af0897fc4e20d95d72b3310"
---

[Discussion](https://hashnode.com/posts/automate-supabase-database-backups-using-github-actions/6966fd0107e1f88430202be6)

Comment [Automate Supabase Database Backups Using GitHub Actions](https://hashnode.com/posts/automate-supabase-database-backups-using-github-actions/6966fd0107e1f88430202be6)

[Vlad Tkachenko](https://hashnode.com/@vladtkdev)

[3d ago](https://hashnode.com/posts/automate-supabase-database-backups-using-github-actions/6966fd0107e1f88430202be6/comment/6af0897fc4e20d95d72b3310)

Useful post, and the IPv6 diagnosis is the part most of these guides miss.

One thing to check in Step 1 though: the string you landed on uses the pooler's user with the direct connection's host. The shared pooler answers on `aws-[INDEX]-[REGION].pooler.supabase.com`, not `db.[ref].supabase.co`. And 6543 is transaction mode, which Supabase's connection guide puts outside pg\_dump, under "migrations, pg\_dump, backup and restore, or replication... single sessions and Postgres native commands". Session mode, 5432 on that pooler host, is the one it offers "when you connect from an IPv4-only network". Same fix you were reaching for, one port down.

Two for the restore post, from a drill we ran on 4 October: `roles.sql` stops on `ALTER ROLE "supabase_admin"` and on `GRANT SET ON PARAMETER`, and pg\_cron jobs do not come back, because they are rows in `cron.job` the data dump skips. Written up at [reeve.page/blog/how-to-restore-a-supabase-backup](https://reeve.page/blog/how-to-restore-a-supabase-backup)