| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Mike Christensen <mike(at)kitchenpc(dot)com>, 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-12 02:22:50 |
| Message-ID: | 1347416570.16640.7.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2012-09-11 at 01:21 -0400, Tom Lane wrote:
> Mike Christensen <mike(at)kitchenpc(dot)com> writes:
> > Oh reading the online docs, it looks like what I may have wanted was:
> > --format=custom
>
> Right. That does everything tar format does, only better --- the only
> thing tar format beats it at is you can disassemble it with tar. Back
> in the day that seemed like a nice thing, open standards and all; but
> the 8GB per file limit is starting to get annoying.
We could change the tar code to produce POSIX 2001 format archives,
which don't have that limitation. But if someone wanted to do some work
in this area, it might be more useful to look into a zip-based format.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wells Oliver | 2012-09-12 02:41:20 | Why is my view making my disk churn? (iostat) |
| Previous Message | Vincent Dautremont | 2012-09-11 20:48:57 | Windows Services and Postgresql 9.1.3 |