| From: | "Rob Dean" <rob(dot)dean(at)pressassociation(dot)com> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | BUG #5343: Documentation error for pg_dump |
| Date: | 2010-02-23 11:37:38 |
| Message-ID: | 201002231137.o1NBbcuR029117@wwwmaster.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 5343
Logged by: Rob Dean
Email address: rob(dot)dean(at)pressassociation(dot)com
PostgreSQL version: 8.3
Operating system: linux
Description: Documentation error for pg_dump
Details:
The last sentence of the penultimate paragraph in the Description for
pg_dump in the Documentation states :-
"The tar format (-Ft) is not compressed and it is not possible to reorder
data when loading, but it is otherwise quite flexible; moreover, it can be
manipulated with standard Unix tools such as tar."
and the description of the tar format option states :-
"t
tar
Output a tar archive suitable for input into pg_restore. Using this archive
format allows reordering and/or exclusion of database objects at the time
the database is restored. It is also possible to limit which data is
reloaded at restore time. "
The information on reordering at restore time is surely completely
contradictory between the two. The 8.4 documentation is the same.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Renner | 2010-02-23 13:22:14 | Re: BUG #5103: "pg_ctl -w (re)start" fails with custom unix_socket_directory |
| Previous Message | Shilpa.R | 2010-02-23 10:40:32 | BUG #5342: Error |