Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xM2V8-00000001p5U-1hY5 for pgsql-announce@arkaria.postgresql.org; Wed, 28 Oct 2026 12:11:31 +0000 Received: from localhost ([127.0.0.1]:38070 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xM2V7-0000000G7de-3gMZ for pgsql-announce@arkaria.postgresql.org; Wed, 28 Oct 2026 12:11:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:40510) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xM2V7-0000000G7cp-0Z8t for pgsql-announce@lists.postgresql.org; Wed, 28 Oct 2026 12:11:29 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xM2V3-00000001Pfi-1tDK for pgsql-announce@lists.postgresql.org; Wed, 28 Oct 2026 12:11:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=AOc652fYEcE2jThDj/8/fRWDSt9Ggn6ElQNw9T9fw4I=; b=si8W1yx/Sw6HAvTua/Vfsu1Y74 qXZPnPwRCcGA/goyrsrWRc2xSeuAuGGb+KkPWoaIuXSLN2KipZYEuLP7C6Mx2l0WV0iwPrkb5bFMX ++g8q4J0m7fgt6DnbNot1mVtRYXC2ZTHSNPY8/RBScf6bmz/NkQGz2M5ng6NO+H8UX4qvqnlpAs1l KcnTegTdI8MTdKoknO6WEHjMDpRwsUMWbZcDs0eVM3UDso67q+shJNB8j+W5n3mRupE9U4P0Hw7Pq gqQB+Dg58vhMGQrPNv4oARBMQoBq2et4WPLTUektc2Gz3NR4dfzZS8wlNg3v/ZX7se6Xv7cSxc3qK qO4qN8wA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xM2V2-00000003v0S-0MQG for pgsql-announce@lists.postgresql.org; Wed, 28 Oct 2026 12:11:24 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xM1q3-00000004BmY-0BnX for pgsql-announce@lists.postgresql.org; Wed, 28 Oct 2026 11:29:03 +0000 Content-Type: multipart/alternative; boundary="===============6782450926260987863==" MIME-Version: 1.0 Subject: ReviveDB: Supabase backups restore-tested against the source schema To: PostgreSQL Announce From: ReviveDB via PostgreSQL Announce Reply-To: support@revivedb.dev Date: Wed, 28 Oct 2026 11:28:20 +0000 Message-ID: <179318690026.1249.3761797662889179732@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: proprietary X-pglister-tagsig: 49bd4d5197f8666b8e22c884b4fa77a3622355a6674d0bde97b4aebf18c5dcde List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============6782450926260987863== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ReviveDB backs up Supabase projects on Postgres 17 outside Supabase, and re= stores 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, colu= mns, constraints, indexes, sequences, views, functions, triggers, RLS polic= ies, grants and extensions. Row counts alone miss a restore that loses a co= nstraint 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 d= ata, 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) --===============6782450926260987863== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ReviveDB: Supabase backups restore-tested against the source sch= ema
 

ReviveDB: Supabase backups restore-tested against the source schema

ReviveDB backs up Supabase projects on Post= gres 17 outside Supabase, and restores every database backup into a tempora= ry PostgreSQL database before it counts as verified.

The restore is compared with an inventory o= f the source: tables, rows, columns, constraints, indexes, sequences, views= , functions, triggers, RLS policies, grants and extensions. Row counts alon= e miss a restore that loses a constraint or a policy.

Each backup run uses its own short-lived, r= ead-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 Supaba= se project, or into the original after a rehearsal on a copy. Free for one = project: https://revivedb.dev

This email was sent to you from ReviveDB. It was delivered on their behalf = by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to ReviveDB.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Proprietary. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============6782450926260987863==--