| Реклама: |
pg_dump [ dbname ]
pg_dump [ -h host ] [ -p port ]
[ -t table ]
[ -f outputfile ]
[ -a ] [ -c ] [ -d ] [ -D ] [ -n ] [ -N ]
[ -o ] [ -s ] [ -u ] [ -v ] [ -x ]
[ dbname ]pg_dump accepts the following command line arguments:
Specifies the name of the database to be extracted. dbname defaults to the value of the USER environment variable.
Dump out only the data, no schema (definitions).
Clean(drop) schema prior to create.
Dump data as proper insert strings.
Dump data as inserts with attribute names
Specifies the output file. Defaults to stdout.
Suppress double quotes around identifiers unless absolutely necessary. This may cause trouble loading this dumped data if there are reserved words used for identifiers. This was the default behavior in pre-v6.4 pg_dump.
Include double quotes around identifiers. This is the default.
Dump object identifiers (OIDs) for every table.
Dump out only the schema (definitions), no data.
Dump data for table only.
Use password authentication. Prompts for username and password.
Specifies verbose mode
Prevent dumping of ACLs (grant/revoke commands) and table ownership information.
pg_dump also accepts the following command line arguments for connection parameters:
Specifies the hostname of the machine on which the postmaster is running. Defaults to using a local Unix domain socket rather than an IP connection..
Specifies the Internet TCP/IP port or local Unix domain socket file extension on which the postmaster is listening for connections. The port number defaults to 5432, or the value of the PGPORT environment variable (if set).
Use password authentication. Prompts for username and password.
pg_dump will create a file or write to stdout.
pg_dump could not attach to the postmaster process on the specified host and port. If you see this message, ensure that the postmaster is running on the proper host and that you have specified the proper port. If your site uses an authentication system, ensure that you have obtained the required authentication credentials.
You do not have a valid entry in the relation pg_shadow and and will not be allowed to access Postgres. Contact your Postgres administrator.
You do not have permission to read the database. Contact your Postgres site administrator.
Note: pg_dump internally executes SELECT statements. If you have problems running pg_dump, make sure you are able to select information from the database using, for example, psql.
pg_dump is a utility for dumping out a Postgres database into a script file containing query commands. The script files are in text format and can be used to reconstruct the database, even on other machines and other architectures. pg_dump will produce the queries necessary to re-generate all user-defined types, functions, tables, indices, aggregates, and operators. In addition, all the data is copied out in text format so that it can be readily copied in again, as well as imported into tools for editing.
pg_dump is useful for dumping out the contents of a database to move from one Postgres installation to another. After running pg_dump, one should examine the output script file for any warnings, especially in light of the limitations listed below.
pg_dump has a few limitations. The limitations mostly stem from difficulty in extracting certain meta-information from the system catalogs.
pg_dump does not understand partial indices. The reason is the same as above; partial index predicates are stored as plans.
pg_dump does not handle large objects. Large objects are ignored and must be dealt with manually.