</html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <link rel="STYLESHEET" type="text/css" href="pgadmin3.css"> <title>Backup</title> </head> <body> <h3>Backup</h3> <center><img src="images/backup.png"> <img src="images/backup-2.png"></center><br/> <center><img src="images/backup-3.png"> <img src="images/backup-4.png"></center> <p> The backup dialogue presents a somewhat simplified interface to the PostgreSQL <a href="http://www.postgresql.org/docs/current/interactive/app-pgdump.html">pg_dump</A> tool. You can backup a single table, a schema or a complete database, dependent on the object you select when starting the backup tool. </p> <p> pg_dump does not support all options for all backup file formats. Particularly, to backup blobs the PLAIN format can not be used. Also, a PLAIN file can not be interpreted, and can not be restored using pgAdmin. The PLAIN format will create an SQL script that can be executed using the psql tool. For standard backup and restore purposes, the COMPRESS and TAR options are recommended. </p> </p> In order to use backup, the pg_dump tool must be accessible by pgAdmin. This can be accomplished by having it locatable using the path, or by copying it into the same directory where the pgadmin3 executable resides. <p> </body> </html>
distrib
>
Fedora
>
13
>
i386
>
media
>
updates
>
by-pkgid
>
cb664fc35171072d04824accda2566aa
>
files
>
146
