From: ReviveDB via PostgreSQL Announce <announce-noreply@postgresql.org>
To: PostgreSQL Announce <pgsql-announce@lists.postgresql.org>
Subject: ReviveDB: Supabase backups restore-tested against the source schema
Date: Wed, 28 Oct 2026 11:28:20 +0000
Message-ID: <179318690026.1249.3761797662889179732@wrigleys.postgresql.org> (raw)
ReviveDB backs up Supabase projects on Postgres 17 outside Supabase, and restores every database backup into a temporary PostgreSQL database before it counts as verified.
The restore is compared with an inventory of the source: tables, rows, columns, constraints, indexes, sequences, views, functions, triggers, RLS policies, grants and extensions. Row counts alone miss a restore that loses a constraint or a policy.
Each backup run uses its own short-lived, read-only Postgres role that also reads rows behind row-level security. The same recovery point holds Auth data, Storage files and Edge Functions.
A recovery point restores into a new Supabase project, or into the original after a rehearsal on a copy. Free for one project: [https://revivedb.dev](https://revivedb.dev)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-announce@postgresql.org
Cc: announce-noreply@postgresql.org, pgsql-announce@lists.postgresql.org
Subject: Re: ReviveDB: Supabase backups restore-tested against the source schema
In-Reply-To: <179318690026.1249.3761797662889179732@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox