pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedpg_dump
5+ messages / 5 participants
[nested] [flat]
* pg_dump
@ 2001-02-26 22:17 Pierce Tyler <pierce@greatbridge.com>
2001-02-27 00:56 ` Re: pg_dump Thomas Lockhart <lockhart@alumni.caltech.edu>
0 siblings, 1 reply; 5+ messages in thread
From: Pierce Tyler @ 2001-02-26 22:17 UTC (permalink / raw)
To: lockhart@fourpalms.org; +Cc: pgsql-docs
Noticed a couple of typos in the pg_dump docs (Reference Guide).
Suggested corrections attached.
Pierce
--
--------------------------------------------------------------
Pierce Tyler | e: pierce@greatbridge.com
Technical Writer | p: (757)233-5544
Great Bridge, LLC | w: www.greatbridge.com
www.greatbridge.org
Attachments:
pg_dump.sgml.diff (text/plain, 1.6K) download
*** ref-symlink/pg_dump.sgml Mon Dec 25 18:15:26 2000
--- pg_dump.sgml Mon Feb 26 16:49:38 2001
***************
*** 475,481 ****
<para>
When used with one of the alternate file formats and combined with
<APPLICATION>pg_restore</APPLICATION>, it provides a flexible archival
! and trasfer mechanism. <APPLICATION>pg_dump</APPLICATION> can be used
to backup an entire database, then <APPLICATION>pg_restore</APPLICATION>
can be used to examine the archive and/or select which parts of the
database are to be restored.
--- 475,481 ----
<para>
When used with one of the alternate file formats and combined with
<APPLICATION>pg_restore</APPLICATION>, it provides a flexible archival
! and transfer mechanism. <APPLICATION>pg_dump</APPLICATION> can be used
to backup an entire database, then <APPLICATION>pg_restore</APPLICATION>
can be used to examine the archive and/or select which parts of the
database are to be restored.
***************
*** 513,519 ****
<para>
When dumping a single table or as plain text, <application>pg_dump</application>
does not handle large objects. Large objects must be dumped in their
! entirity using one of the binary archive formats.
</para>
</listitem>
--- 513,519 ----
<para>
When dumping a single table or as plain text, <application>pg_dump</application>
does not handle large objects. Large objects must be dumped in their
! entirety using one of the binary archive formats.
</para>
</listitem>
* Re: pg_dump
2001-02-26 22:17 pg_dump Pierce Tyler <pierce@greatbridge.com>
@ 2001-02-27 00:56 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
2001-02-27 02:39 ` Re: Re: pg_dump Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 5+ messages in thread
From: Thomas Lockhart @ 2001-02-27 00:56 UTC (permalink / raw)
To: Pierce Tyler <pierce@greatbridge.com>; pgsql-docs; +Cc: lockhart@fourpalms.org
> Noticed a couple of typos in the pg_dump docs (Reference Guide).
> Suggested corrections attached.
Got it. Thanks.
Peter E and other doc'ers:
While there, I noticed that there were some embedded ^M's at the end of
some lines of text. I have a utility to scrub that cruft off of the end
of lines (it scrubs any non-printable character and any whitespace) and
have run it on all of the ref/ files; some had ^M's and others had some
other kind of whitespace stripped out. Most files got touched.
I'd like to commit these at some point, but perhaps I should wait until
freezing the docs? Which btw is Real Soon Now, since scrappy may be
close to declaring the release date.
Comments?
- Thomas
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Re: pg_dump
2001-02-26 22:17 pg_dump Pierce Tyler <pierce@greatbridge.com>
2001-02-27 00:56 ` Re: pg_dump Thomas Lockhart <lockhart@alumni.caltech.edu>
@ 2001-02-27 02:39 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 5+ messages in thread
From: Tom Lane @ 2001-02-27 02:39 UTC (permalink / raw)
To: lockhart@fourpalms.org; +Cc: Pierce Tyler <pierce@greatbridge.com>; pgsql-docs
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
> While there, I noticed that there were some embedded ^M's at the end of
> some lines of text.
Yeah, I'd griped about that a month or so back, but didn't get around to
doing something about it.
> I have a utility to scrub that cruft off of the end
> of lines (it scrubs any non-printable character and any whitespace) and
> have run it on all of the ref/ files; some had ^M's and others had some
> other kind of whitespace stripped out. Most files got touched.
> I'd like to commit these at some point, but perhaps I should wait until
> freezing the docs?
I'd say commit now, else you'll have to redo the work later. I think we
are still doing minor changes to the docs, but probably nothing major...
regards, tom lane
^ permalink raw reply [nested|flat] 5+ messages in thread
* pg_dump
@ 2005-11-11 23:04 Judith Altamirano Figueroa <jaltamirano@correolux.com.mx>
2005-11-15 12:01 ` Re: [SQL] pg_dump Oliver Elphick <olly@lfix.co.uk>
0 siblings, 1 reply; 5+ messages in thread
From: Judith Altamirano Figueroa @ 2005-11-11 23:04 UTC (permalink / raw)
To: pgsql-sql@postgresql.org
Hi
how could I restore a db if I did next:
pg_dump -Z 9 soi > $DESTINO/soi.bkp
Thanks in advanced
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [SQL] pg_dump
2005-11-11 23:04 pg_dump Judith Altamirano Figueroa <jaltamirano@correolux.com.mx>
@ 2005-11-15 12:01 ` Oliver Elphick <olly@lfix.co.uk>
0 siblings, 0 replies; 5+ messages in thread
From: Oliver Elphick @ 2005-11-15 12:01 UTC (permalink / raw)
To: Judith Altamirano Figueroa <jaltamirano@correolux.com.mx>; +Cc: pgsql-docs; pgsql-sql@postgresql.org
On Fri, 2005-11-11 at 17:04 -0600, Judith Altamirano Figueroa wrote:
> Hi
>
> how could I restore a db if I did next:
>
> pg_dump -Z 9 soi > $DESTINO/soi.bkp
Since you don't specify any dump format, your dump should be plain text
and is compressed with gzip, so the restore command is going to be:
zcat $DESTINO/soi.bkp | psql -d restore_database_name -f -
You have to create the database to restore into first.
------------------------------------------
[Note for documentation:
According to the psql man page:
-Z 0..9
--compress=0..9
Specify the compression level to use in archive formats that
support compression. (Currently only the custom archive format
supports compression.)
However using psql -Z with no format or with "-F p" in fact produces a
gzipped file.]
This might be a suitable amendment to the docs?:
$ diff -u /tmp/pg_dump.sgml.orig /tmp/pg_dump.sgml
inline patch 1: /tmp/pg_dump.sgml (+3/-2 lines) download inline-1.patch
--- /tmp/pg_dump.sgml.orig 2005-11-15 11:50:55.000000000 +0000
+++ /tmp/pg_dump.sgml 2005-11-15 11:57:38.000000000 +0000
@@ -492,8 +492,9 @@
<listitem>
<para>
Specify the compression level to use in archive formats that
- support compression. (Currently only the custom archive
- format supports compression.)
+ support compression. (Currently the tar archive
+ format does not support compression. The plain text format is
+ compressed with gzip.)
</para>
</listitem>
</varlistentry>
end of thread, other threads:[~2005-11-15 12:01 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2001-02-26 22:17 pg_dump Pierce Tyler <pierce@greatbridge.com>
2001-02-27 00:56 ` Thomas Lockhart <lockhart@alumni.caltech.edu>
2001-02-27 02:39 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-11-11 23:04 pg_dump Judith Altamirano Figueroa <jaltamirano@correolux.com.mx>
2005-11-15 12:01 ` Oliver Elphick <olly@lfix.co.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox