Problem Current backup jobs appear to use default pg_dump settings (likely plain text). On disk-constrained hosts this leads to failures. Backups failed due to “No space left on device.”

Please add a way to configure pg_dump flags in the Backup settings UI so we can enable compression and other options. Without compression, dump sizes are significantly larger than necessary.

Desired Outcome In Backup Settings, allow selecting/customizing pg_dump parameters, for example:

• Dump format: -Fc (custom, compressed) and -F p (plain)
• Compression level: -Z 0..9 (default sensible value, e.g., 6)
• Parallel workers: -j N (when server/connection supports it)
• Include blobs: --blobs (toggle)
• Ownership/privileges: --no-owner, --no-privileges (toggles)
• Table/schema filters: --table, --exclude-table, --schema, --exclude-schema
• Lock/timeout: --lock-wait-timeout=…
• Clean/if-exists flags for restore convenience (exposed as “include drop statements on restore” hint)

In simplest case - allow anything as a plain text input which is appedned tot he pg_dump command.

Benefits Reduced backup size → fewer “no space left on device” failures. Faster backups/restores in many cases (parallelism). Greater control for different deployment constraints.