From 85e623b469cd273f9a91c3e5071ced3bcbfc6305 Mon Sep 17 00:00:00 2001 From: Tom Gallacher Date: Tue, 10 Mar 2026 14:56:03 +0000 Subject: [PATCH] docs(backups): physical backups are enabled by default (#43192) ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? doc ## What is the current behavior? Doc incorrectly states physical backups are not enabled by default. ## What is the new behavior? Backup doc page now correctly clarifies physical backups are enabled by default, assuming project is eligible. ## Additional context NA --------- Co-authored-by: Chris Chinchilla Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- apps/docs/content/guides/platform/backups.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/apps/docs/content/guides/platform/backups.mdx b/apps/docs/content/guides/platform/backups.mdx index a08c9585ebf..82091f9a6cb 100644 --- a/apps/docs/content/guides/platform/backups.mdx +++ b/apps/docs/content/guides/platform/backups.mdx @@ -13,6 +13,18 @@ When you delete a project, we permanently remove all associated data, including +## Types of backups + +Database backups can be categorized into two types: **logical** and **physical**. You can learn more about them [in this blog post](/blog/postgresql-physical-logical-backups). + + + +All projects on Postgres `15.8.1.079` and newer use the newer physical backup process. + +Projects on older Postgres versions have to upgrade in order to be transitioned to physical backups. Once upgraded to an eligible version, your project is automatically transitioned over to physical backups. + + + For security purposes, daily backups do not store passwords for custom roles, and you will not find them in downloadable files. If you restore from a daily backup and use custom roles, you will need to reset their passwords after the restoration completes.