lywsvip/supabase
1
0
Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-07-07 03:34:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

Docs: clarifying PITR behavior when disabled (#37539)

Browse Source
This commit is contained in:
Monica Khoury
2025-07-29 17:32:14 +02:00
committed by GitHub
parent c386daf3a0
commit 87fceafaeb
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
apps/docs/content/guides/platform/backups.mdx
View File

@@ -131,6 +131,14 @@ If you enable PITR, Daily Backups will no longer be taken. PITR provides a finer
</Admonition>
When you disable PITR, all new backups will still be taken as physical backups only. Physical backups can still be used for restoration, but they are not available for direct download. If you need to download a backup after PITR is disabled, you’ll need to take a manual logical backup using the Supabase CLI or pg_dump.
<Admonition type="note">
If PITR has been disabled, logical backups remain available until they pass the backup retention period for your plan. After that window passes, only physical backups will be shown.
</Admonition>
### Backup process [#pitr-backup-process]
As discussed [here](https://supabase.com/blog/postgresql-physical-logical-backups), PITR is made possible by a combination of taking physical backups of a project, as well as archiving [Write Ahead Log (WAL)](https://www.postgresql.org/docs/current/wal-intro.html) files. Physical backups provide a snapshot of the underlying directory of the database, while WAL files contain records of every change made in the database.