| From: | "Nick Fankhauser" <nickf(at)ontko(dot)com> |
|---|---|
| To: | "Sam Barnett-Cormack" <s(dot)barnett-cormack(at)lancaster(dot)ac(dot)uk>, "Nick Fankhauser" <nickf(at)ontko(dot)com> |
| Cc: | "pgsql-admin" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Error message using pg_dump with tar format |
| Date: | 2003-07-07 16:47:25 |
| Message-ID: | NEBBLAAHGLEEPCGOBHDGKEGAHLAA.nickf@ontko.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> Does it stop at a filesize limit imposed by the OS or filesystem, such
> as 2.0GB as commonly found on linux, or NFS?
No, in this case, it is stopping at about 1.3 GB uncompressed. I usually
pipe the pg_dump output into gzip but removed the gzip to simplify the
situation while testing. Under normal circumstances, I run both a text dump
and a tar format dump each night. The text format runs to completion and
uses about 600MB, while the tar format version quits with the errror at
150MB.
(good thought though!)
-NF
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2003-07-07 17:03:24 | Re: Advantages and disadvantages of more than one dbserver |
| Previous Message | Sam Barnett-Cormack | 2003-07-07 16:42:40 | Re: Error message using pg_dump with tar format |