1999-07-22 17:09:15 +02:00
|
|
|
<!--
|
2001-03-06 19:55:57 +01:00
|
|
|
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.30 2001/03/06 18:55:57 petere Exp $
|
1999-07-22 17:09:15 +02:00
|
|
|
Postgres documentation
|
|
|
|
-->
|
|
|
|
|
|
|
|
<refentry id="APP-PGDUMP">
|
2000-12-26 00:15:27 +01:00
|
|
|
<docinfo>
|
2001-03-06 19:55:57 +01:00
|
|
|
<date>2001-03-06</date>
|
2000-12-26 00:15:27 +01:00
|
|
|
</docinfo>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<refmeta>
|
2001-03-06 19:55:57 +01:00
|
|
|
<refentrytitle>
|
|
|
|
pg_dump
|
1999-07-06 19:16:42 +02:00
|
|
|
</refentrytitle>
|
2000-12-26 00:15:27 +01:00
|
|
|
<manvolnum>1</manvolnum>
|
1999-07-06 19:16:42 +02:00
|
|
|
<refmiscinfo>Application</refmiscinfo>
|
|
|
|
</refmeta>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<refnamediv>
|
2001-03-06 19:55:57 +01:00
|
|
|
<refname>pg_dump</refname>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<refpurpose>
|
2000-11-21 16:39:09 +01:00
|
|
|
Extract a <productname>Postgres</productname> database into a script file or other archive file
|
1999-07-06 19:16:42 +02:00
|
|
|
</refpurpose>
|
|
|
|
</refnamediv>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<refsynopsisdiv>
|
2001-03-06 19:55:57 +01:00
|
|
|
<cmdsynopsis>
|
|
|
|
<command>pg_dump</command>
|
|
|
|
<group> <arg>-a</arg> <arg>-s</arg> </group>
|
|
|
|
<arg>-b</arg>
|
|
|
|
<arg>-c</arg>
|
|
|
|
<arg>-C</arg>
|
|
|
|
<group> <arg>-d</arg> <arg>-D</arg> </group>
|
|
|
|
<arg>-f <replaceable>file</replaceable></arg>
|
|
|
|
<arg>-F <replaceable>format</replaceable></arg>
|
|
|
|
<arg>-i</arg>
|
|
|
|
<sbr>
|
|
|
|
<group> <arg>-n</arg> <arg>-N</arg> </group>
|
|
|
|
<arg>-o</arg>
|
|
|
|
<arg>-O</arg>
|
|
|
|
<arg>-R</arg>
|
|
|
|
<arg>-S</arg>
|
|
|
|
<arg>-t <replaceable>table</replaceable></arg>
|
|
|
|
<arg>-v</arg>
|
|
|
|
<arg>-x</arg>
|
|
|
|
<arg>-Z <replaceable>0...9</replaceable></arg>
|
|
|
|
<sbr>
|
|
|
|
<arg>-h <replaceable>host</replaceable></arg>
|
|
|
|
<arg>-p <replaceable>port</replaceable></arg>
|
|
|
|
<arg>-u</arg>
|
|
|
|
<sbr>
|
|
|
|
<arg choice="plain"><replaceable>dbname</replaceable></arg>
|
|
|
|
</cmdsynopsis>
|
|
|
|
</refsynopsisdiv>
|
|
|
|
|
|
|
|
|
|
|
|
<refsect1 id="pg-dump-description">
|
|
|
|
<title>
|
|
|
|
Description
|
|
|
|
</title>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
<command>pg_dump</command> is a utility for dumping out a
|
|
|
|
<productname>Postgres</productname> database into a script or archive
|
|
|
|
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.
|
|
|
|
The archive files, new with version 7.1, contain enough information for
|
|
|
|
<xref linkend="app-pgrestore"> to rebuild the database, but also
|
|
|
|
allow <command>pg_restore</command> to be selective about what is restored, or even to
|
|
|
|
reorder the items prior to being restored. The archive files are
|
|
|
|
also designed to be portable across architectures.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
<command>pg_dump</command>
|
|
|
|
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.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
<command>pg_dump</command>
|
|
|
|
is useful for dumping out the contents of a database to move from one
|
|
|
|
<productname>Postgres</productname> installation to another. After running
|
|
|
|
<command>pg_dump</command>,
|
|
|
|
one should examine the output for any warnings, especially
|
|
|
|
in light of the limitations listed below.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
When used with one of the alternate file formats and combined with
|
|
|
|
<command>pg_restore</command>, it provides a flexible archival
|
|
|
|
and transfer mechanism. <command>pg_dump</command> can be used
|
|
|
|
to backup an entire database, then <command>pg_restore</command>
|
|
|
|
can be used to examine the archive and/or select which parts of the
|
|
|
|
database are to be restored.
|
|
|
|
See the <xref linkend="app-pgrestore"> documentation for details.
|
|
|
|
</para>
|
|
|
|
|
|
|
|
<refsect2 id="pg-dump-options">
|
|
|
|
<title>Options</title>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> accepts the following command
|
|
|
|
line arguments. (Long option forms are only available on some platforms.)
|
1999-07-06 19:16:42 +02:00
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term><replaceable class="parameter">dbname</replaceable></term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies the name of the database to be extracted.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-a</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--data-only</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Dump only the data, not the schema (definitions).
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-05 19:42:57 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term>-b</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--blobs</term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Dump data and <acronym>BLOB</acronym> data.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-c</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--clean</term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Dump commands to clean (drop) the schema prior to (the
|
|
|
|
commands for) creating it.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-C</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--create</term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
For plain text (script) output, include commands to create the database itself.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term>-d</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--inserts</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Dump data as proper <command>INSERT</command> commands (not
|
|
|
|
<command>COPY</command>). This will make restoration very
|
|
|
|
slow.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-D</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--attribute-inserts</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Dump data as <command>INSERT</command> commands with explicit
|
|
|
|
column names. This will make restoration very slow.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2001-03-05 19:42:57 +01:00
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-f <replaceable class="parameter">file</replaceable></term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--file=<replaceable class="parameter">file</replaceable></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Send output to the specified file.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-F <replaceable class="parameter">format</replaceable></term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--format=<replaceable class="parameter">format</replaceable></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Format can be one of the following:
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term>p</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
output a plain text <acronym>SQL</acronym> script file (default)
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>t</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
output a <filename>tar</filename> archive suitable for input into
|
|
|
|
<command>pg_restore</command>. Using this archive format
|
2001-03-05 19:42:57 +01:00
|
|
|
allows reordering and/or exclusion of schema elements
|
|
|
|
at the time the database is restored. It is also possible to limit
|
|
|
|
which data is reloaded at restore time.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>c</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
output a custom archive suitable for input into
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_restore</command>. This is the most flexible
|
2001-03-05 19:42:57 +01:00
|
|
|
format in that it allows reordering of data load as well
|
|
|
|
as schema elements. This format is also compressed by default.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
</variablelist>
|
2001-03-06 19:55:57 +01:00
|
|
|
</para>
|
2001-03-05 19:42:57 +01:00
|
|
|
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
1999-07-06 19:16:42 +02:00
|
|
|
|
2000-04-04 07:22:46 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term>-i</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--ignore-version</term>
|
2000-04-04 07:22:46 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Ignore version mismatch between <command>pg_dump</command>
|
|
|
|
and the database server. Since <command>pg_dump</command>
|
2000-04-04 07:22:46 +02:00
|
|
|
knows a great deal about system catalogs, any given version of
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> is only intended to work with
|
2000-04-04 07:22:46 +02:00
|
|
|
the corresponding release of the database server. Use this option
|
|
|
|
if you need to override the version check (and if
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> then fails, don't
|
2000-04-04 07:22:46 +02:00
|
|
|
say you weren't warned).
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term>-n</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--no-quotes</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Suppress double quotes around identifiers unless absolutely necessary.
|
|
|
|
This may cause trouble loading this dumped data if there are reserved words
|
|
|
|
used for identifiers.
|
2000-03-27 19:14:43 +02:00
|
|
|
This was the default behavior for
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> prior to version 6.4.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-N</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--quotes</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Include double quotes around identifiers.
|
|
|
|
This is the default.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-05 19:42:57 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term>-o</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--oids</term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Dump object identifiers (<acronym>OID</acronym>s) for every table.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-O</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--no-owner</term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
In plain text output mode, do not set object ownership to
|
|
|
|
match the original database. Typically,
|
|
|
|
<command>pg_dump</command> issues
|
|
|
|
(<command>psql</command>-specific) <command>\connect</command>
|
|
|
|
statements to set ownership of schema elements.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-R</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--no-reconnect</term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
In plain text output mode, prohibit <command>pg_dump</command>
|
|
|
|
from issuing any <command>\connect</command> statements.
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term>-s</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--schema-only</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Dump only the schema (definitions), no data.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
2001-03-05 19:42:57 +01:00
|
|
|
<varlistentry>
|
|
|
|
<term>-S <replaceable class="parameter">username</replaceable></term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--superuser=<replaceable class="parameter">username</replaceable></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Specify the superuser user name to use when disabling triggers and/or
|
2001-03-05 19:42:57 +01:00
|
|
|
setting ownership of schema elements.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-t <replaceable class="parameter">table</replaceable></term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--table=<replaceable class="parameter">table</replaceable></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Dump data for <replaceable class="parameter">table</replaceable> only.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
<varlistentry>
|
|
|
|
<term>-v</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--verbose</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2000-10-05 21:48:34 +02:00
|
|
|
Specifies verbose mode.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-x</term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--no-acl</term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Prevent dumping of ACLs (grant/revoke commands) and table ownership information.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
2001-03-05 19:42:57 +01:00
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-Z <replaceable class="parameter">0..9</replaceable></term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--compress=<replaceable class="parameter">0..9</replaceable></term>
|
2001-03-05 19:42:57 +01:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specify the compression level to use in archive formats that support
|
|
|
|
compression (currently only the custom archive format supports compression).
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> also accepts
|
1999-07-06 19:16:42 +02:00
|
|
|
the following command line arguments for connection parameters:
|
|
|
|
|
|
|
|
<variablelist>
|
|
|
|
<varlistentry>
|
|
|
|
<term>-h <replaceable class="parameter">host</replaceable></term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--host=<replaceable class="parameter">host</replaceable></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
Specifies the host name of the machine on which the
|
|
|
|
<command>postmaster</command>
|
2000-11-14 00:57:20 +01:00
|
|
|
is running. If host begins with a slash, it is used
|
2001-03-06 19:55:57 +01:00
|
|
|
as the directory for the Unix domain socket.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-p <replaceable class="parameter">port</replaceable></term>
|
2001-03-06 19:55:57 +01:00
|
|
|
<term>--port=<replaceable class="parameter">port</replaceable></term>
|
1999-07-06 19:16:42 +02:00
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Specifies the Internet TCP/IP port or local Unix domain socket file
|
2001-03-06 19:55:57 +01:00
|
|
|
extension on which the <command>postmaster</command>
|
1999-07-06 19:16:42 +02:00
|
|
|
is listening for connections. The port number defaults to 5432,
|
|
|
|
or the value of the <envar>PGPORT</envar>
|
|
|
|
environment variable (if set).
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
|
|
|
|
<varlistentry>
|
|
|
|
<term>-u</term>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
|
|
|
Use password authentication.
|
|
|
|
Prompts for
|
|
|
|
<replaceable class="parameter">username</replaceable>
|
|
|
|
and <replaceable class="parameter">password</replaceable>.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
</varlistentry>
|
|
|
|
</variablelist>
|
|
|
|
</para>
|
|
|
|
</refsect2>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
</refsect1>
|
1999-07-06 19:16:42 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<refsect1 id="app-pgdump-diagnostics">
|
|
|
|
<title>Diagnostics</title>
|
|
|
|
|
|
|
|
<msgset>
|
|
|
|
<msgentry>
|
|
|
|
<msg>
|
|
|
|
<msgmain>
|
|
|
|
<msgtext>
|
|
|
|
<screen><computeroutput>
|
1999-07-06 19:16:42 +02:00
|
|
|
Connection to database 'template1' failed.
|
2000-12-01 00:20:51 +01:00
|
|
|
connectDBStart() -- connect() failed: No such file or directory
|
|
|
|
Is the postmaster running locally
|
|
|
|
and accepting connections on Unix socket '/tmp/.s.PGSQL.5432'?
|
2001-03-06 19:55:57 +01:00
|
|
|
</computeroutput></screen>
|
|
|
|
</msgtext>
|
|
|
|
</msgmain>
|
|
|
|
</msg>
|
|
|
|
|
|
|
|
<msgexplan>
|
1999-07-06 19:16:42 +02:00
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> could not attach to the
|
|
|
|
<command>postmaster</command>
|
1999-07-06 19:16:42 +02:00
|
|
|
process on the specified host and port. If you see this message,
|
2001-03-06 19:55:57 +01:00
|
|
|
ensure that the <command>postmaster</command>
|
1999-07-06 19:16:42 +02:00
|
|
|
is running on the proper host and that you have specified the proper
|
2001-03-06 19:55:57 +01:00
|
|
|
port.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
2001-03-06 19:55:57 +01:00
|
|
|
</msgexplan>
|
|
|
|
</msgentry>
|
|
|
|
|
|
|
|
<msgentry>
|
|
|
|
<msg>
|
|
|
|
<msgmain>
|
|
|
|
<msgtext>
|
|
|
|
<screen><computeroutput>
|
1999-07-06 19:16:42 +02:00
|
|
|
dumpSequence(<replaceable class="parameter">table</replaceable>): SELECT failed
|
2001-03-06 19:55:57 +01:00
|
|
|
</computeroutput></screen>
|
|
|
|
</msgtext>
|
|
|
|
</msgmain>
|
|
|
|
</msg>
|
|
|
|
|
|
|
|
<msgexplan>
|
1999-07-06 19:16:42 +02:00
|
|
|
<para>
|
|
|
|
You do not have permission to read the database.
|
|
|
|
Contact your <productname>Postgres</productname> site administrator.
|
|
|
|
</para>
|
2001-03-06 19:55:57 +01:00
|
|
|
</msgexplan>
|
|
|
|
</msgentry>
|
|
|
|
</msgset>
|
1999-07-06 19:16:42 +02:00
|
|
|
|
|
|
|
<note>
|
1998-12-29 03:24:47 +01:00
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> internally executes
|
1999-07-06 19:16:42 +02:00
|
|
|
<command>SELECT</command> statements. If you have problems running
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command>,
|
1999-07-06 19:16:42 +02:00
|
|
|
make sure you are able to select information from the database using, for
|
2001-03-06 19:55:57 +01:00
|
|
|
example, <xref linkend="app-psql">.
|
1998-12-29 03:24:47 +01:00
|
|
|
</para>
|
1999-07-06 19:16:42 +02:00
|
|
|
</note>
|
|
|
|
</refsect1>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<refsect1 id="pg-dump-notes">
|
|
|
|
<title>Notes</title>
|
1999-07-06 19:16:42 +02:00
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
<command>pg_dump</command> has a few limitations.
|
1999-07-06 19:16:42 +02:00
|
|
|
The limitations mostly stem from
|
|
|
|
difficulty in extracting certain meta-information from the system
|
|
|
|
catalogs.
|
|
|
|
|
|
|
|
<itemizedlist>
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
When dumping a single table or as plain text, <command>pg_dump</command>
|
2001-03-05 19:42:57 +01:00
|
|
|
does not handle large objects. Large objects must be dumped in their
|
2001-03-06 19:55:57 +01:00
|
|
|
entirety using one of the binary archive formats.
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
</listitem>
|
2000-04-11 16:43:54 +02:00
|
|
|
|
|
|
|
<listitem>
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
When doing a data only dump, <command>pg_dump</command> emits queries
|
2000-04-11 16:43:54 +02:00
|
|
|
to disable triggers on user tables before inserting the data and queries to
|
2000-07-22 06:45:10 +02:00
|
|
|
re-enable them after the data has been inserted. If the restore is stopped
|
2000-04-11 16:43:54 +02:00
|
|
|
in the middle, the system catalogs may be left in the wrong state.
|
|
|
|
</para>
|
|
|
|
</listitem>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
</itemizedlist>
|
|
|
|
</para>
|
|
|
|
</refsect1>
|
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<refsect1 id="pg-dump-examples">
|
|
|
|
<title>Examples</title>
|
1999-07-06 19:16:42 +02:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<para>
|
|
|
|
To dump a database:
|
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump mydb > db.out</userinput>
|
|
|
|
</screen>
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
|
|
|
To reload this database:
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>psql -d database -f db.out</userinput>
|
|
|
|
</screen>
|
1999-07-06 19:16:42 +02:00
|
|
|
</para>
|
2001-03-05 19:42:57 +01:00
|
|
|
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
To dump a database called mydb that contains
|
|
|
|
<acronym>BLOB</acronym>s to a <filename>tar</filename> file:
|
2001-03-05 19:42:57 +01:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_dump -Ft -b mydb > db.tar</userinput>
|
|
|
|
</screen>
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
|
|
|
|
<para>
|
2001-03-06 19:55:57 +01:00
|
|
|
To reload this database (with <acronym>BLOB</acronym>s) to an
|
|
|
|
existing database called newdb:
|
2001-03-05 19:42:57 +01:00
|
|
|
|
2001-03-06 19:55:57 +01:00
|
|
|
<screen>
|
|
|
|
<prompt>$</prompt> <userinput>pg_restore -d newdb db.tar</userinput>
|
|
|
|
</screen>
|
2001-03-05 19:42:57 +01:00
|
|
|
</para>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
</refsect1>
|
2001-03-06 19:55:57 +01:00
|
|
|
|
|
|
|
<refsect1>
|
|
|
|
<title>See Also</title>
|
|
|
|
|
|
|
|
<simplelist type="inline">
|
|
|
|
<member><xref linkend="app-pg-dumpall"></member>
|
|
|
|
<member><xref linkend="app-pgrestore"></member>
|
|
|
|
<member><xref linkend="app-psql"></member>
|
|
|
|
<member><citetitle>PostgreSQL Administrator's Guide</citetitle></member>
|
|
|
|
</simplelist>
|
|
|
|
</refsect1>
|
|
|
|
|
1999-07-06 19:16:42 +02:00
|
|
|
</refentry>
|
|
|
|
|
|
|
|
<!-- Keep this comment at the end of the file
|
|
|
|
Local variables:
|
|
|
|
mode: sgml
|
|
|
|
sgml-omittag:nil
|
|
|
|
sgml-shorttag:t
|
|
|
|
sgml-minimize-attributes:nil
|
|
|
|
sgml-always-quote-attributes:t
|
|
|
|
sgml-indent-step:1
|
|
|
|
sgml-indent-data:t
|
|
|
|
sgml-parent-document:nil
|
|
|
|
sgml-default-dtd-file:"../reference.ced"
|
|
|
|
sgml-exposed-tags:nil
|
|
|
|
sgml-local-catalogs:"/usr/lib/sgml/catalog"
|
|
|
|
sgml-local-ecat-files:nil
|
|
|
|
End:
|
|
|
|
-->
|