| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mike Christensen <mike(at)kitchenpc(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Bad pg_dump error message |
| Date: | 2012-09-11 05:26:47 |
| Message-ID: | 10970.1347341207@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Mike Christensen <mike(at)kitchenpc(dot)com> writes:
>> Is the TAR format just the raw SQL commands, just tar'ed and then sent
>> over the wire?
Sorta. If you pull it apart with tar, you'll find out there's a SQL
script that creates the database schema, and then a separate tar-member
file containing the data for each table.
Custom format goes this a little better by splitting the information up
into a separate archive item for each database object. But there's no
tool other than pg_restore that knows how to deconstruct custom-format
archives.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gustav Potgieter | 2012-09-11 10:56:41 | Postgresql replication assistance |
| Previous Message | Mike Christensen | 2012-09-11 05:24:20 | Re: Bad pg_dump error message |