Logical backup contains PostgreSQL 17.6+ commands incompatible with PostgreSQL 15.8 (source db)

## Problem Description Logical backups downloaded from the Supabase Dashboard contain `\restrict` and `\unrestrict` commands that were introduced in PostgreSQL 17.6. When attempting to restore these backups to a PostgreSQL 15.8 database (the same version as the production database), the restore fails because these commands are not recognized. ## Expected Behavior Backups generated from a PostgreSQL 15.8 database should be compatible with PostgreSQL 15.8, allowing restoration to the same version. ## Actual Behavior The restore fails with: ``` invalid command \restrict ``` ## Environment - **Production Database**: PostgreSQL 15.8 - **Target Database**: PostgreSQL 15.8 (same version as production) - **Backup Source**: Supabase Dashboard (logical backup) - **Backup Format**: Contains PostgreSQL 17.6+ specific commands (`\restrict`, `\unrestrict`) ## Workaround Manually removing the `\restrict` and `\unrestrict` commands from the backup file allows the restore to complete successfully. ## Questions - Why does Supabase generate backups with PostgreSQL 17.6+ features when the source database is PostgreSQL 15.8? - Is Supabase's backup infrastructure running a newer PostgreSQL version than the customer's database? ## Additional Context According to [PostgreSQL 17.6 release notes](https://www.postgresql.org/docs/17/release-17-6.html), the `\restrict` command was introduced as a security feature (CVE-2025-8714) to prevent malicious dumps from executing shell commands via psql meta-commands. The `pg_dump` tool was updated to issue `\restrict` before any data from the source server. However, this creates a compatibility issue when restoring backups to older PostgreSQL versions that don't recognize this command. ## Related - PostgreSQL 17.6 Release Notes: https://www.postgresql.org/docs/17/release-17-6.html