PgSql备份pg_dump与还原手记pg_restore(国外英语资料).docVIP

PgSql备份pg_dump与还原手记pg_restore(国外英语资料) PgSql backup pg_dump and restore manual pg_restore (turn) I didnt think it was a PostgreSQL user who suddenly needed a library transplant. It turns out that its quite different from the mysql command line. Dont be afraid, but be careful, because database operations are the core of the site, and if there is any damage or loss, the consequences are very serious. I wrote the steps first and then went as planned, although there was a mistake, but eventually it was a safe transplant. This is on record for later use. The backup restore method: pg_dump and pg_restore, first specify the two commands and then record my methods. Pg_dump - pulls a PostgreSQL database into a script file or other archive Pg_dump [option...] [dbname] Option option... The following command line parameters control the content and format of the output. dbname Declare the database name to be dumped. If this parameter is not declared, then the environment variable PGDATABASE is used. If the environment variable is not declared, use the user name that initiates the connection. - a - data - only Output data, not output mode (data definition). This option only makes sense for plain text format. For the archive format, you can declare options when calling pg_restore. - b - blobs Contain large objects in the dump. A non-text output format must be selected. - c - the clean The output removes the command from the database object before creating the database creation command. This option only makes sense for plain text format. For the archive format, you can declare options when calling pg_restore. - C - create The output is started with a command that creates the database itself and is linked to the database. (if its this form of script, it doesnt matter which database connection you have before running the script.) This option only makes sense for plain text format. For the archive format, you can declare this option when calling pg_restore. - d - inserts INSERT the dat