Baoding-FenShuaJiang
/
Green_GoodERP18_FSJ_Standard
關註 1
收藏 0
Wiki 捐赠
gooderp18绿色标准版
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
目錄樹: 0f75e31513
分支列表 標籤列表
${ item.name }
Create branch ${ searchTerm }
from '0f75e31513'
${ noResults }
Green_GoodERP18_FSJ_Standard/PostgreSQL/doc/postgresql/html/app-pgrestore.html

488 line
38KB
原始文件 Blame 文件歷史 

  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>

  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>pg_restore</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="app-pgrecvlogical.html" title="pg_recvlogical" /><link rel="next" href="app-psql.html" title="psql" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">pg_restore</th></tr><tr><td width="10%" align="left"><a accesskey="p" href="app-pgrecvlogical.html" title="pg_recvlogical">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="reference-client.html" title="PostgreSQL Client Applications">Up</a></td><th width="60%" align="center">PostgreSQL Client Applications</th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 12.4 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="app-psql.html" title="psql">Next</a></td></tr></table><hr></hr></div><div class="refentry" id="APP-PGRESTORE"><div class="titlepage"></div><a id="id-1.9.4.17.1" class="indexterm"></a><div class="refnamediv"><h2><span class="refentrytitle">pg_restore</span></h2><p>pg_restore — 

  3.    restore a <span class="productname">PostgreSQL</span> database from an

  4.    archive file created by <span class="application">pg_dump</span>

  5.   </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p id="id-1.9.4.17.4.1"><code class="command">pg_restore</code> [<em class="replaceable"><code>connection-option</code></em>...] [<em class="replaceable"><code>option</code></em>...] [<em class="replaceable"><code>filename</code></em>]</p></div></div><div class="refsect1" id="APP-PGRESTORE-DESCRIPTION"><h2>Description</h2><p>

  6.    <span class="application">pg_restore</span> is a utility for restoring a

  7.    <span class="productname">PostgreSQL</span> database from an archive

  8.    created by <a class="xref" href="app-pgdump.html" title="pg_dump"><span class="refentrytitle">pg_dump</span></a> in one of the non-plain-text

  9.    formats.  It will issue the commands necessary to reconstruct the

  10.    database to the state it was in at the time it was saved.  The

  11.    archive files also allow <span class="application">pg_restore</span> to

  12.    be selective about what is restored, or even to reorder the items

  13.    prior to being restored. The archive files are designed to be

  14.    portable across architectures.

  15.   </p><p>

  16.    <span class="application">pg_restore</span> can operate in two modes.

  17.    If a database name is specified, <span class="application">pg_restore</span>

  18.    connects to that database and restores archive contents directly into

  19.    the database.  Otherwise, a script containing the SQL

  20.    commands necessary to rebuild the database is created and written

  21.    to a file or standard output.  This script output is equivalent to

  22.    the plain text output format of <span class="application">pg_dump</span>.

  23.    Some of the options controlling the output are therefore analogous to

  24.    <span class="application">pg_dump</span> options.

  25.   </p><p>

  26.    Obviously, <span class="application">pg_restore</span> cannot restore information

  27.    that is not present in the archive file.  For instance, if the

  28.    archive was made using the <span class="quote">“<span class="quote">dump data as

  29.    <code class="command">INSERT</code> commands</span>”</span> option,

  30.    <span class="application">pg_restore</span> will not be able to load the data

  31.    using <code class="command">COPY</code> statements.

  32.   </p></div><div class="refsect1" id="APP-PGRESTORE-OPTIONS"><h2>Options</h2><p>

  33.     <span class="application">pg_restore</span> accepts the following command

  34.     line arguments.

  35. 

  36.     </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="replaceable"><code>filename</code></em></span></dt><dd><p>

  37.        Specifies the location of the archive file (or directory, for a

  38.        directory-format archive) to be restored.

  39.        If not specified, the standard input is used.

  40.        </p></dd><dt><span class="term"><code class="option">-a</code><br /></span><span class="term"><code class="option">--data-only</code></span></dt><dd><p>

  41.         Restore only the data, not the schema (data definitions).

  42.         Table data, large objects, and sequence values are restored,

  43.         if present in the archive.

  44.        </p><p>

  45.         This option is similar to, but for historical reasons not identical

  46.         to, specifying <code class="option">--section=data</code>.

  47.        </p></dd><dt><span class="term"><code class="option">-c</code><br /></span><span class="term"><code class="option">--clean</code></span></dt><dd><p>

  48.         Clean (drop) database objects before recreating them.

  49.         (Unless <code class="option">--if-exists</code> is used,

  50.         this might generate some harmless error messages, if any objects

  51.         were not present in the destination database.)

  52.        </p></dd><dt><span class="term"><code class="option">-C</code><br /></span><span class="term"><code class="option">--create</code></span></dt><dd><p>

  53.         Create the database before restoring into it.

  54.         If <code class="option">--clean</code> is also specified, drop and

  55.         recreate the target database before connecting to it.

  56.        </p><p>

  57.         With <code class="option">--create</code>, <span class="application">pg_restore</span>

  58.         also restores the database's comment if any, and any configuration

  59.         variable settings that are specific to this database, that is,

  60.         any <code class="command">ALTER DATABASE ... SET ...</code>

  61.         and <code class="command">ALTER ROLE ... IN DATABASE ... SET ...</code>

  62.         commands that mention this database.

  63.         Access privileges for the database itself are also restored,

  64.         unless <code class="option">--no-acl</code> is specified.

  65.        </p><p>

  66.         When this option is used, the database named with <code class="option">-d</code>

  67.         is used only to issue the initial <code class="command">DROP DATABASE</code> and

  68.         <code class="command">CREATE DATABASE</code> commands.  All data is restored into the

  69.         database name that appears in the archive.

  70.        </p></dd><dt><span class="term"><code class="option">-d <em class="replaceable"><code>dbname</code></em></code><br /></span><span class="term"><code class="option">--dbname=<em class="replaceable"><code>dbname</code></em></code></span></dt><dd><p>

  71.         Connect to database <em class="replaceable"><code>dbname</code></em> and restore directly

  72.         into the database.

  73.        </p></dd><dt><span class="term"><code class="option">-e</code><br /></span><span class="term"><code class="option">--exit-on-error</code></span></dt><dd><p>

  74.         Exit if an error is encountered while sending SQL commands to

  75.         the database. The default is to continue and to display a count of

  76.         errors at the end of the restoration.

  77.        </p></dd><dt><span class="term"><code class="option">-f <em class="replaceable"><code>filename</code></em></code><br /></span><span class="term"><code class="option">--file=<em class="replaceable"><code>filename</code></em></code></span></dt><dd><p>

  78.         Specify output file for generated script, or for the listing

  79.         when used with <code class="option">-l</code>. Use <code class="literal">-</code>

  80.         for <span class="systemitem">stdout</span>.

  81.        </p></dd><dt><span class="term"><code class="option">-F <em class="replaceable"><code>format</code></em></code><br /></span><span class="term"><code class="option">--format=<em class="replaceable"><code>format</code></em></code></span></dt><dd><p>

  82.         Specify format of the archive.  It is not necessary to specify

  83.         the format, since <span class="application">pg_restore</span> will

  84.         determine the format automatically. If specified, it can be

  85.         one of the following:

  86. 

  87.        </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="literal">c</code><br /></span><span class="term"><code class="literal">custom</code></span></dt><dd><p>

  88.            The archive is in the custom format of

  89.            <span class="application">pg_dump</span>.

  90.           </p></dd><dt><span class="term"><code class="literal">d</code><br /></span><span class="term"><code class="literal">directory</code></span></dt><dd><p>

  91.            The archive is a directory archive.

  92.           </p></dd><dt><span class="term"><code class="literal">t</code><br /></span><span class="term"><code class="literal">tar</code></span></dt><dd><p>

  93.            The archive is a <code class="command">tar</code> archive.

  94.           </p></dd></dl></div></dd><dt><span class="term"><code class="option">-I <em class="replaceable"><code>index</code></em></code><br /></span><span class="term"><code class="option">--index=<em class="replaceable"><code>index</code></em></code></span></dt><dd><p>

  95.         Restore definition of named index only.  Multiple indexes

  96.         may be specified with multiple <code class="option">-I</code> switches.

  97.        </p></dd><dt><span class="term"><code class="option">-j <em class="replaceable"><code>number-of-jobs</code></em></code><br /></span><span class="term"><code class="option">--jobs=<em class="replaceable"><code>number-of-jobs</code></em></code></span></dt><dd><p>

  98.         Run the most time-consuming steps

  99.         of <span class="application">pg_restore</span> — those that load data,

  100.         create indexes, or create constraints — concurrently, using up

  101.         to <em class="replaceable"><code>number-of-jobs</code></em>

  102.         concurrent sessions.  This option can dramatically reduce the time

  103.         to restore a large database to a server running on a

  104.         multiprocessor machine.  This option is ignored when emitting a script

  105.         rather than connecting directly to a database server.

  106.        </p><p>

  107.         Each job is one process or one thread, depending on the

  108.         operating system, and uses a separate connection to the

  109.         server.

  110.        </p><p>

  111.         The optimal value for this option depends on the hardware

  112.         setup of the server, of the client, and of the network.

  113.         Factors include the number of CPU cores and the disk setup.  A

  114.         good place to start is the number of CPU cores on the server,

  115.         but values larger than that can also lead to faster restore

  116.         times in many cases.  Of course, values that are too high will

  117.         lead to decreased performance because of thrashing.

  118.        </p><p>

  119.         Only the custom and directory archive formats are supported

  120.         with this option.

  121.         The input must be a regular file or directory (not, for example, a

  122.         pipe or standard input).  Also, multiple

  123.         jobs cannot be used together with the

  124.         option <code class="option">--single-transaction</code>.

  125.        </p></dd><dt><span class="term"><code class="option">-l</code><br /></span><span class="term"><code class="option">--list</code></span></dt><dd><p>

  126.         List the table of contents of the archive. The output of this operation

  127.         can be used as input to the <code class="option">-L</code> option.  Note that

  128.         if filtering switches such as <code class="option">-n</code> or <code class="option">-t</code> are

  129.         used with <code class="option">-l</code>, they will restrict the items listed.

  130.        </p></dd><dt><span class="term"><code class="option">-L <em class="replaceable"><code>list-file</code></em></code><br /></span><span class="term"><code class="option">--use-list=<em class="replaceable"><code>list-file</code></em></code></span></dt><dd><p>

  131.         Restore only those archive elements that are listed in <em class="replaceable"><code>list-file</code></em>, and restore them in the

  132.         order they appear in the file.  Note that

  133.         if filtering switches such as <code class="option">-n</code> or <code class="option">-t</code> are

  134.         used with <code class="option">-L</code>, they will further restrict the items restored.

  135.        </p><p><em class="replaceable"><code>list-file</code></em> is normally created by

  136.         editing the output of a previous <code class="option">-l</code> operation.

  137.         Lines can be moved or removed, and can also

  138.         be commented out by placing a semicolon (<code class="literal">;</code>) at the

  139.         start of the line.  See below for examples.

  140.        </p></dd><dt><span class="term"><code class="option">-n <em class="replaceable"><code>schema</code></em></code><br /></span><span class="term"><code class="option">--schema=<em class="replaceable"><code>schema</code></em></code></span></dt><dd><p>

  141.         Restore only objects that are in the named schema.  Multiple schemas

  142.         may be specified with multiple <code class="option">-n</code> switches.  This can be

  143.         combined with the <code class="option">-t</code> option to restore just a

  144.         specific table.

  145.        </p></dd><dt><span class="term"><code class="option">-N <em class="replaceable"><code>schema</code></em></code><br /></span><span class="term"><code class="option">--exclude-schema=<em class="replaceable"><code>schema</code></em></code></span></dt><dd><p>

  146.         Do not restore objects that are in the named schema.  Multiple schemas

  147.         to be excluded may be specified with multiple <code class="option">-N</code> switches.

  148.        </p><p>

  149.         When both <code class="option">-n</code> and <code class="option">-N</code> are given for the same

  150.         schema name, the <code class="option">-N</code> switch wins and the schema is excluded.

  151.        </p></dd><dt><span class="term"><code class="option">-O</code><br /></span><span class="term"><code class="option">--no-owner</code></span></dt><dd><p>

  152.         Do not output commands to set

  153.         ownership of objects to match the original database.

  154.         By default, <span class="application">pg_restore</span> issues

  155.         <code class="command">ALTER OWNER</code> or

  156.         <code class="command">SET SESSION AUTHORIZATION</code>

  157.         statements to set ownership of created schema elements.

  158.         These statements will fail unless the initial connection to the

  159.         database is made by a superuser

  160.         (or the same user that owns all of the objects in the script).

  161.         With <code class="option">-O</code>, any user name can be used for the

  162.         initial connection, and this user will own all the created objects.

  163.        </p></dd><dt><span class="term"><code class="option">-P <em class="replaceable"><code>function-name(argtype [, ...])</code></em></code><br /></span><span class="term"><code class="option">--function=<em class="replaceable"><code>function-name(argtype [, ...])</code></em></code></span></dt><dd><p>

  164.         Restore the named function only.  Be careful to spell the function

  165.         name and arguments exactly as they appear in the dump file's table

  166.         of contents.  Multiple functions may be specified with multiple

  167.         <code class="option">-P</code> switches.

  168.        </p></dd><dt><span class="term"><code class="option">-R</code><br /></span><span class="term"><code class="option">--no-reconnect</code></span></dt><dd><p>

  169.         This option is obsolete but still accepted for backwards

  170.         compatibility.

  171.        </p></dd><dt><span class="term"><code class="option">-s</code><br /></span><span class="term"><code class="option">--schema-only</code></span></dt><dd><p>

  172.         Restore only the schema (data definitions), not data,

  173.         to the extent that schema entries are present in the archive.

  174.        </p><p>

  175.         This option is the inverse of <code class="option">--data-only</code>.

  176.         It is similar to, but for historical reasons not identical to,

  177.         specifying

  178.         <code class="option">--section=pre-data --section=post-data</code>.

  179.        </p><p>

  180.         (Do not confuse this with the <code class="option">--schema</code> option, which

  181.         uses the word <span class="quote">“<span class="quote">schema</span>”</span> in a different meaning.)

  182.        </p></dd><dt><span class="term"><code class="option">-S <em class="replaceable"><code>username</code></em></code><br /></span><span class="term"><code class="option">--superuser=<em class="replaceable"><code>username</code></em></code></span></dt><dd><p>

  183.         Specify the superuser user name to use when disabling triggers.

  184.         This is relevant only if <code class="option">--disable-triggers</code> is used.

  185.        </p></dd><dt><span class="term"><code class="option">-t <em class="replaceable"><code>table</code></em></code><br /></span><span class="term"><code class="option">--table=<em class="replaceable"><code>table</code></em></code></span></dt><dd><p>

  186.         Restore definition and/or data of only the named table.

  187.         For this purpose, <span class="quote">“<span class="quote">table</span>”</span> includes views, materialized views,

  188.         sequences, and foreign tables.  Multiple tables

  189.         can be selected by writing multiple <code class="option">-t</code> switches.

  190.         This option can be combined with the <code class="option">-n</code> option to

  191.         specify table(s) in a particular schema.

  192.        </p><div class="note"><h3 class="title">Note</h3><p>

  193.          When <code class="option">-t</code> is specified, <span class="application">pg_restore</span>

  194.          makes no attempt to restore any other database objects that the

  195.          selected table(s) might depend upon.  Therefore, there is no

  196.          guarantee that a specific-table restore into a clean database will

  197.          succeed.

  198.         </p></div><div class="note"><h3 class="title">Note</h3><p>

  199.          This flag does not behave identically to the <code class="option">-t</code>

  200.          flag of <span class="application">pg_dump</span>.  There is not currently

  201.          any provision for wild-card matching in <span class="application">pg_restore</span>,

  202.          nor can you include a schema name within its <code class="option">-t</code>.

  203.          And, while <span class="application">pg_dump</span>'s <code class="option">-t</code>

  204.          flag will also dump subsidiary objects (such as indexes) of the

  205.          selected table(s),

  206.          <span class="application">pg_restore</span>'s <code class="option">-t</code>

  207.          flag does not include such subsidiary objects.

  208.         </p></div><div class="note"><h3 class="title">Note</h3><p>

  209.          In versions prior to <span class="productname">PostgreSQL</span> 9.6, this flag

  210.          matched only tables, not any other type of relation.

  211.         </p></div></dd><dt><span class="term"><code class="option">-T <em class="replaceable"><code>trigger</code></em></code><br /></span><span class="term"><code class="option">--trigger=<em class="replaceable"><code>trigger</code></em></code></span></dt><dd><p>

  212.         Restore named trigger only.  Multiple triggers may be specified with

  213.         multiple <code class="option">-T</code> switches.

  214.        </p></dd><dt><span class="term"><code class="option">-v</code><br /></span><span class="term"><code class="option">--verbose</code></span></dt><dd><p>

  215.         Specifies verbose mode.

  216.        </p></dd><dt><span class="term"><code class="option">-V</code><br /></span><span class="term"><code class="option">--version</code></span></dt><dd><p>

  217.        Print the <span class="application">pg_restore</span> version and exit.

  218.        </p></dd><dt><span class="term"><code class="option">-x</code><br /></span><span class="term"><code class="option">--no-privileges</code><br /></span><span class="term"><code class="option">--no-acl</code></span></dt><dd><p>

  219.         Prevent restoration of access privileges (grant/revoke commands).

  220.        </p></dd><dt><span class="term"><code class="option">-1</code><br /></span><span class="term"><code class="option">--single-transaction</code></span></dt><dd><p>

  221.         Execute the restore as a single transaction (that is, wrap the

  222.         emitted commands in <code class="command">BEGIN</code>/<code class="command">COMMIT</code>).  This

  223.         ensures that either all the commands complete successfully, or no

  224.         changes are applied. This option implies

  225.         <code class="option">--exit-on-error</code>.

  226.        </p></dd><dt><span class="term"><code class="option">--disable-triggers</code></span></dt><dd><p>

  227.         This option is relevant only when performing a data-only restore.

  228.         It instructs <span class="application">pg_restore</span> to execute commands

  229.         to temporarily disable triggers on the target tables while

  230.         the data is reloaded.  Use this if you have referential

  231.         integrity checks or other triggers on the tables that you

  232.         do not want to invoke during data reload.

  233.        </p><p>

  234.         Presently, the commands emitted for

  235.         <code class="option">--disable-triggers</code> must be done as superuser.  So you

  236.         should also specify a superuser name with <code class="option">-S</code> or,

  237.         preferably, run <span class="application">pg_restore</span> as a

  238.         <span class="productname">PostgreSQL</span> superuser.

  239.        </p></dd><dt><span class="term"><code class="option">--enable-row-security</code></span></dt><dd><p>

  240.         This option is relevant only when restoring the contents of a table

  241.         which has row security.  By default, <span class="application">pg_restore</span> will set

  242.         <a class="xref" href="runtime-config-client.html#GUC-ROW-SECURITY">row_security</a> to off, to ensure

  243.         that all data is restored in to the table.  If the user does not have

  244.         sufficient privileges to bypass row security, then an error is thrown.

  245.         This parameter instructs <span class="application">pg_restore</span> to set

  246.         <a class="xref" href="runtime-config-client.html#GUC-ROW-SECURITY">row_security</a> to on instead, allowing the user to attempt to restore

  247.         the contents of the table with row security enabled.  This might still

  248.         fail if the user does not have the right to insert the rows from the

  249.         dump into the table.

  250.        </p><p>

  251.         Note that this option currently also requires the dump be in <code class="command">INSERT</code>

  252.         format, as <code class="command">COPY FROM</code> does not support row security.

  253.        </p></dd><dt><span class="term"><code class="option">--if-exists</code></span></dt><dd><p>

  254.         Use conditional commands (i.e. add an <code class="literal">IF EXISTS</code>

  255.         clause) to drop database objects.  This option is not valid

  256.         unless <code class="option">--clean</code> is also specified.

  257.        </p></dd><dt><span class="term"><code class="option">--no-comments</code></span></dt><dd><p>

  258.         Do not output commands to restore comments, even if the archive

  259.         contains them.

  260.        </p></dd><dt><span class="term"><code class="option">--no-data-for-failed-tables</code></span></dt><dd><p>

  261.         By default, table data is restored even if the creation command

  262.         for the table failed (e.g., because it already exists).

  263.         With this option, data for such a table is skipped.

  264.         This behavior is useful if the target database already

  265.         contains the desired table contents.  For example,

  266.         auxiliary tables for <span class="productname">PostgreSQL</span> extensions

  267.         such as <span class="productname">PostGIS</span> might already be loaded in

  268.         the target database; specifying this option prevents duplicate

  269.         or obsolete data from being loaded into them.

  270.        </p><p>

  271.         This option is effective only when restoring directly into a

  272.         database, not when producing SQL script output.

  273.        </p></dd><dt><span class="term"><code class="option">--no-publications</code></span></dt><dd><p>

  274.         Do not output commands to restore publications, even if the archive

  275.         contains them.

  276.        </p></dd><dt><span class="term"><code class="option">--no-security-labels</code></span></dt><dd><p>

  277.         Do not output commands to restore security labels,

  278.         even if the archive contains them.

  279.        </p></dd><dt><span class="term"><code class="option">--no-subscriptions</code></span></dt><dd><p>

  280.         Do not output commands to restore subscriptions, even if the archive

  281.         contains them.

  282.        </p></dd><dt><span class="term"><code class="option">--no-tablespaces</code></span></dt><dd><p>

  283.         Do not output commands to select tablespaces.

  284.         With this option, all objects will be created in whichever

  285.         tablespace is the default during restore.

  286.        </p></dd><dt><span class="term"><code class="option">--section=<em class="replaceable"><code>sectionname</code></em></code></span></dt><dd><p>

  287.           Only restore the named section. The section name can be

  288.           <code class="option">pre-data</code>, <code class="option">data</code>, or <code class="option">post-data</code>.

  289.           This option can be specified more than once to select multiple

  290.           sections. The default is to restore all sections.

  291.          </p><p>

  292.           The data section contains actual table data as well as large-object

  293.           definitions.

  294.           Post-data items consist of definitions of indexes, triggers, rules

  295.           and constraints other than validated check constraints.

  296.           Pre-data items consist of all other data definition items.

  297.          </p></dd><dt><span class="term"><code class="option">--strict-names</code></span></dt><dd><p>

  298.         Require that each schema

  299.         (<code class="option">-n</code>/<code class="option">--schema</code>) and table

  300.         (<code class="option">-t</code>/<code class="option">--table</code>) qualifier match at

  301.         least one schema/table in the backup file.

  302.        </p></dd><dt><span class="term"><code class="option">--use-set-session-authorization</code></span></dt><dd><p>

  303.         Output SQL-standard <code class="command">SET SESSION AUTHORIZATION</code> commands

  304.         instead of <code class="command">ALTER OWNER</code> commands to determine object

  305.         ownership.  This makes the dump more standards-compatible, but

  306.         depending on the history of the objects in the dump, might not restore

  307.         properly.

  308.        </p></dd><dt><span class="term"><code class="option">-?</code><br /></span><span class="term"><code class="option">--help</code></span></dt><dd><p>

  309.        Show help about <span class="application">pg_restore</span> command line

  310.        arguments, and exit.

  311.        </p></dd></dl></div><p>

  312.    </p><p>

  313.     <span class="application">pg_restore</span> also accepts

  314.     the following command line arguments for connection parameters:

  315. 

  316.     </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="option">-h <em class="replaceable"><code>host</code></em></code><br /></span><span class="term"><code class="option">--host=<em class="replaceable"><code>host</code></em></code></span></dt><dd><p>

  317.         Specifies the host name of the machine on which the server is

  318.         running.  If the value begins with a slash, it is used as the

  319.         directory for the Unix domain socket. The default is taken

  320.         from the <code class="envar">PGHOST</code> environment variable, if set,

  321.         else a Unix domain socket connection is attempted.

  322.        </p></dd><dt><span class="term"><code class="option">-p <em class="replaceable"><code>port</code></em></code><br /></span><span class="term"><code class="option">--port=<em class="replaceable"><code>port</code></em></code></span></dt><dd><p>

  323.         Specifies the TCP port or local Unix domain socket file

  324.         extension on which the server is listening for connections.

  325.         Defaults to the <code class="envar">PGPORT</code> environment variable, if

  326.         set, or a compiled-in default.

  327.         </p></dd><dt><span class="term"><code class="option">-U <em class="replaceable"><code>username</code></em></code><br /></span><span class="term"><code class="option">--username=<em class="replaceable"><code>username</code></em></code></span></dt><dd><p>

  328.         User name to connect as.

  329.        </p></dd><dt><span class="term"><code class="option">-w</code><br /></span><span class="term"><code class="option">--no-password</code></span></dt><dd><p>

  330.         Never issue a password prompt.  If the server requires

  331.         password authentication and a password is not available by

  332.         other means such as a <code class="filename">.pgpass</code> file, the

  333.         connection attempt will fail.  This option can be useful in

  334.         batch jobs and scripts where no user is present to enter a

  335.         password.

  336.        </p></dd><dt><span class="term"><code class="option">-W</code><br /></span><span class="term"><code class="option">--password</code></span></dt><dd><p>

  337.         Force <span class="application">pg_restore</span> to prompt for a

  338.         password before connecting to a database.

  339.        </p><p>

  340.         This option is never essential, since

  341.         <span class="application">pg_restore</span> will automatically prompt

  342.         for a password if the server demands password authentication.

  343.         However, <span class="application">pg_restore</span> will waste a

  344.         connection attempt finding out that the server wants a password.

  345.         In some cases it is worth typing <code class="option">-W</code> to avoid the extra

  346.         connection attempt.

  347.        </p></dd><dt><span class="term"><code class="option">--role=<em class="replaceable"><code>rolename</code></em></code></span></dt><dd><p>

  348.         Specifies a role name to be used to perform the restore.

  349.         This option causes <span class="application">pg_restore</span> to issue a

  350.         <code class="command">SET ROLE</code> <em class="replaceable"><code>rolename</code></em>

  351.         command after connecting to the database. It is useful when the

  352.         authenticated user (specified by <code class="option">-U</code>) lacks privileges

  353.         needed by <span class="application">pg_restore</span>, but can switch to a role with

  354.         the required rights.  Some installations have a policy against

  355.         logging in directly as a superuser, and use of this option allows

  356.         restores to be performed without violating the policy.

  357.        </p></dd></dl></div><p>

  358.    </p></div><div class="refsect1" id="id-1.9.4.17.7"><h2>Environment</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="envar">PGHOST</code><br /></span><span class="term"><code class="envar">PGOPTIONS</code><br /></span><span class="term"><code class="envar">PGPORT</code><br /></span><span class="term"><code class="envar">PGUSER</code></span></dt><dd><p>

  359.       Default connection parameters

  360.      </p></dd><dt><span class="term"><code class="envar">PG_COLOR</code></span></dt><dd><p>

  361.       Specifies whether to use color in diagnostic messages. Possible values

  362.       are <code class="literal">always</code>, <code class="literal">auto</code> and

  363.       <code class="literal">never</code>.

  364.      </p></dd></dl></div><p>

  365.    This utility, like most other <span class="productname">PostgreSQL</span> utilities,

  366.    also uses the environment variables supported by <span class="application">libpq</span>

  367.    (see <a class="xref" href="libpq-envars.html" title="33.14. Environment Variables">Section 33.14</a>).  However, it does not read

  368.    <code class="envar">PGDATABASE</code> when a database name is not supplied.

  369.   </p></div><div class="refsect1" id="APP-PGRESTORE-DIAGNOSTICS"><h2>Diagnostics</h2><p>

  370.    When a direct database connection is specified using the

  371.    <code class="option">-d</code> option, <span class="application">pg_restore</span>

  372.    internally executes <acronym class="acronym">SQL</acronym> statements. If you have

  373.    problems running <span class="application">pg_restore</span>, make sure

  374.    you are able to select information from the database using, for

  375.    example, <a class="xref" href="app-psql.html" title="psql"><span class="refentrytitle"><span class="application">psql</span></span></a>.  Also, any default connection

  376.    settings and environment variables used by the

  377.    <span class="application">libpq</span> front-end library will apply.

  378.   </p></div><div class="refsect1" id="APP-PGRESTORE-NOTES"><h2>Notes</h2><p>

  379.    If your installation has any local additions to the

  380.    <code class="literal">template1</code> database, be careful to load the output of

  381.    <span class="application">pg_restore</span> into a truly empty database;

  382.    otherwise you are likely to get errors due to duplicate definitions

  383.    of the added objects.  To make an empty database without any local

  384.    additions, copy from <code class="literal">template0</code> not <code class="literal">template1</code>, for example:

  385. </p><pre class="programlisting">

  386. CREATE DATABASE foo WITH TEMPLATE template0;

  387. </pre><p>

  388.   </p><p>

  389.    The limitations of <span class="application">pg_restore</span> are detailed below.

  390. 

  391.    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>

  392.       When restoring data to a pre-existing table and the option

  393.       <code class="option">--disable-triggers</code> is used,

  394.       <span class="application">pg_restore</span> emits commands

  395.       to disable triggers on user tables before inserting the data, then emits commands to

  396.       re-enable them after the data has been inserted.  If the restore is stopped in the

  397.       middle, the system catalogs might be left in the wrong state.

  398.      </p></li><li class="listitem"><p><span class="application">pg_restore</span> cannot restore large objects

  399.       selectively;  for instance, only those for a specific table.  If

  400.       an archive contains large objects, then all large objects will be

  401.       restored, or none of them if they are excluded via <code class="option">-L</code>,

  402.       <code class="option">-t</code>, or other options.

  403.      </p></li></ul></div><p>

  404.   </p><p>

  405.    See also the <a class="xref" href="app-pgdump.html" title="pg_dump"><span class="refentrytitle">pg_dump</span></a> documentation for details on

  406.    limitations of <span class="application">pg_dump</span>.

  407.   </p><p>

  408.    Once restored, it is wise to run <code class="command">ANALYZE</code> on each

  409.    restored table so the optimizer has useful statistics; see

  410.    <a class="xref" href="routine-vacuuming.html#VACUUM-FOR-STATISTICS" title="24.1.3. Updating Planner Statistics">Section 24.1.3</a> and

  411.    <a class="xref" href="routine-vacuuming.html#AUTOVACUUM" title="24.1.6. The Autovacuum Daemon">Section 24.1.6</a> for more information.

  412.   </p></div><div class="refsect1" id="APP-PGRESTORE-EXAMPLES"><h2>Examples</h2><p>

  413.    Assume we have dumped a database called <code class="literal">mydb</code> into a

  414.    custom-format dump file:

  415. 

  416. </p><pre class="screen">

  417. <code class="prompt">$</code> <strong class="userinput"><code>pg_dump -Fc mydb &gt; db.dump</code></strong>

  418. </pre><p>

  419.   </p><p>

  420.    To drop the database and recreate it from the dump:

  421. 

  422. </p><pre class="screen">

  423. <code class="prompt">$</code> <strong class="userinput"><code>dropdb mydb</code></strong>

  424. <code class="prompt">$</code> <strong class="userinput"><code>pg_restore -C -d postgres db.dump</code></strong>

  425. </pre><p>

  426. 

  427.    The database named in the <code class="option">-d</code> switch can be any database existing

  428.    in the cluster; <span class="application">pg_restore</span> only uses it to issue the

  429.    <code class="command">CREATE DATABASE</code> command for <code class="literal">mydb</code>.  With

  430.    <code class="option">-C</code>, data is always restored into the database name that appears

  431.    in the dump file.

  432.   </p><p>

  433.    To reload the dump into a new database called <code class="literal">newdb</code>:

  434. 

  435. </p><pre class="screen">

  436. <code class="prompt">$</code> <strong class="userinput"><code>createdb -T template0 newdb</code></strong>

  437. <code class="prompt">$</code> <strong class="userinput"><code>pg_restore -d newdb db.dump</code></strong>

  438. </pre><p>

  439. 

  440.    Notice we don't use <code class="option">-C</code>, and instead connect directly to the

  441.    database to be restored into.  Also note that we clone the new database

  442.    from <code class="literal">template0</code> not <code class="literal">template1</code>, to ensure it is

  443.    initially empty.

  444.   </p><p>

  445.    To reorder database items, it is first necessary to dump the table of

  446.    contents of the archive:

  447. </p><pre class="screen">

  448. <code class="prompt">$</code> <strong class="userinput"><code>pg_restore -l db.dump &gt; db.list</code></strong>

  449. </pre><p>

  450.    The listing file consists of a header and one line for each item, e.g.:

  451. </p><pre class="programlisting">

  452. ;

  453. ; Archive created at Mon Sep 14 13:55:39 2009

  454. ;     dbname: DBDEMOS

  455. ;     TOC Entries: 81

  456. ;     Compression: 9

  457. ;     Dump Version: 1.10-0

  458. ;     Format: CUSTOM

  459. ;     Integer: 4 bytes

  460. ;     Offset: 8 bytes

  461. ;     Dumped from database version: 8.3.5

  462. ;     Dumped by pg_dump version: 8.3.8

  463. ;

  464. ;

  465. ; Selected TOC Entries:

  466. ;

  467. 3; 2615 2200 SCHEMA - public pasha

  468. 1861; 0 0 COMMENT - SCHEMA public pasha

  469. 1862; 0 0 ACL - public pasha

  470. 317; 1247 17715 TYPE public composite pasha

  471. 319; 1247 25899 DOMAIN public domain0 pasha

  472. </pre><p>

  473.    Semicolons start a comment, and the numbers at the start of lines refer to the

  474.    internal archive ID assigned to each item.

  475.   </p><p>

  476.    Lines in the file can be commented out, deleted, and reordered. For example:

  477. </p><pre class="programlisting">

  478. 10; 145433 TABLE map_resolutions postgres

  479. ;2; 145344 TABLE species postgres

  480. ;4; 145359 TABLE nt_header postgres

  481. 6; 145402 TABLE species_records postgres

  482. ;8; 145416 TABLE ss_old postgres

  483. </pre><p>

  484.    could be used as input to <span class="application">pg_restore</span> and would only restore

  485.    items 10 and 6, in that order:

  486. </p><pre class="screen">

  487. <code class="prompt">$</code> <strong class="userinput"><code>pg_restore -L db.list db.dump</code></strong>

  488. </pre></div><div class="refsect1" id="id-1.9.4.17.11"><h2>See Also</h2><span class="simplelist"><a class="xref" href="app-pgdump.html" title="pg_dump"><span class="refentrytitle">pg_dump</span></a>, <a class="xref" href="app-pg-dumpall.html" title="pg_dumpall"><span class="refentrytitle"><span class="application">pg_dumpall</span></span></a>, <a class="xref" href="app-psql.html" title="psql"><span class="refentrytitle"><span class="application">psql</span></span></a></span></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="app-pgrecvlogical.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="reference-client.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="app-psql.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="application">pg_recvlogical</span> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> <span class="application">psql</span></td></tr></table></div></body></html>
上海开阖软件有限公司 沪ICP备12045867号-1