Summary
The "Backup Globals" dialog contains a notification stating that backups will be in PLAIN format, yet the UI does not provide the user with a "Format" selection to confirm or change this, nor does it allow for the selection of specific global objects (Roles vs. Tablespaces).
• Missing Format Selection: While the footer note says, "Only objects global to the entire database will be backed up, in PLAIN format," standard pgAdmin backup dialogs usually offer a dropdown for format (Plain, Custom, Tar, Directory). If a user expects a compressed format to save space on a large cluster, they are forced into PLAIN without a choice in this specific view.
• Filename Extension Validation: The user has entered ab.sql. While technically a plain text extension, if pgAdmin is hardcoded to PLAIN for globals, it should ideally validate or enforce the extension or, at the very least, provide a warning if the user attempts to type an incompatible extension (like .backup).
Steps to Reproduce
- Open pgAdmin 4.
- Right-click on a Server (not a specific database).
- Select Backup Globals...
- Observe the "General" tab and the static notification at the bottom.
Expected Behavior
The UI should ideally:
• Provide a Format dropdown (even if defaulted to Plain) to maintain consistency with the standard "Backup" dialog.
• Provide checkboxes to include/exclude specific global types (e.g., Roles only, Tablespaces only).
• Ensure the footer note dynamically updates if the format were to be changed.
Snapshot 1:
Snapshot 2:
Summary
The "Backup Globals" dialog contains a notification stating that backups will be in PLAIN format, yet the UI does not provide the user with a "Format" selection to confirm or change this, nor does it allow for the selection of specific global objects (Roles vs. Tablespaces).
• Missing Format Selection: While the footer note says, "Only objects global to the entire database will be backed up, in PLAIN format," standard pgAdmin backup dialogs usually offer a dropdown for format (Plain, Custom, Tar, Directory). If a user expects a compressed format to save space on a large cluster, they are forced into PLAIN without a choice in this specific view.
• Filename Extension Validation: The user has entered ab.sql. While technically a plain text extension, if pgAdmin is hardcoded to PLAIN for globals, it should ideally validate or enforce the extension or, at the very least, provide a warning if the user attempts to type an incompatible extension (like .backup).
Steps to Reproduce
Expected Behavior
The UI should ideally:
• Provide a Format dropdown (even if defaulted to Plain) to maintain consistency with the standard "Backup" dialog.
• Provide checkboxes to include/exclude specific global types (e.g., Roles only, Tablespaces only).
• Ensure the footer note dynamically updates if the format were to be changed.
Snapshot 1:
Snapshot 2: