The Backup dialog provides an easy-to-use interface for the pg_dump pg_dump command line utility. Easy to use options allow you to backup a database, a schema definition, data, or an database object.
By selecting fields on the Backup dialog, you specify which options should be included in a customized pg_dump command. The pg_dump command writes an archive that you can use with the pgAdmin’s *Restore* dialog, the psql client , or pg_restore to recreate the objects backed up by the archive.
If you choose to create a plain-text backup, you can review the SQL commands that build the selected object to better help you understand how the object will be recreated. You can also optionally modify the content to create new database objects before restoring.
The drop-down listbox in the Format field allows you to select an archive format. Each format has advantages and disadvantages; select the format that is best suited for your application:
- Select Plain to generate a plain-text script file containing SQL statements and commands that you can execute at the psql command line or with pg_dump to recreate the database objects and load the table data. A plain-text backup file can easily be edited in a text editor if desired before restoring the database objects with the psql program. Plain-text format is normally recommended for smaller databases.
- Select Custom to generate a pg_dump formatted binary file that allows for restoration of all or only selected database objects from the backup file. You can use pgAdmin to restore from a custom archive backup file. A custom archive backup file cannot be edited, but you can use pgAdmin to select which database objects to restore from the backup file. Custom archive format is recommended for medium to large databases from which you may want to select the database objects to restore from the backup file.
- Select Tar to generate a tar archive file that allows for restoration of all or only selected database objects from the backup file. You can use pgAdmin to restore from a tar archive backup file.
- Select Directory to generate a directory-format archive suitable for use with pgAdmin’s Restore dialog or pg_restore. This file format creates a directory with one file for each table and blob being dumped, plus a Table of Contents file describing the dumped objects in a machine-readable format that pg_restore can read. A directory format archive can be manipulated with standard Unix tools; for example, files in an uncompressed archive can be compressed with the gzip tool. This format is compressed by default and supports parallel dumps.
To open the Backup dialog, right click on the name of a database or a named object in the tree control and select Backup… from the context menu. The Backup dialog opens:
Use the fields on the File Options tab to specify general information about the backup.
When you’ve completed the File Options tab, navigate to the Dump Options #1 tab:
Use the fields on the Dump Options #1 tab to specify details about the type of objects that will be backed up:
When you’ve completed the Dump Options #1 tab, select the Dump Options #2 tab:
Use the fields on the Dump Options #2 tab to specify details about the statements used within the backup file.
When you’ve completed the Dump Options #2 tab, select the Objects tab:
Use the fields on the Objects tab to select the objects that will be included in the backup; by default, when performing a database backup, all objects will be selected for inclusion in the archive. Deselect an object name to exclude that object from the archive.
When you’ve specified the details that will be incorporated into the pg_dump command, click the Backup button to build and execute a command based on those preferences; the result will be displayed on the Messages tab:
If the backup is successful, the Messages tab will display:
Process returned exit code 0.
Scroll up to review the pg_dump command used to generate the archive, or to view any error messages that were returned during the backup. When you’re finished, click Done to exit the Backup dialog.