| From: | Mike Christensen <mike(at)kitchenpc(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:24:20 |
| Message-ID: | CABs1bs30giSYxNVpxWkYubOFKT9u=1LDSwWz3CWw8o4BWe+MRw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Sep 10, 2012 at 10:21 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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.
Thanks for your help, Tom!
Next time I'll read the docs. "custom" is kinda a weird name for it,
I think I just kinda glazed over it thinking it was some way to define
my own format or something..
Mike
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-11 05:26:47 | Re: Bad pg_dump error message |
| Previous Message | Tom Lane | 2012-09-11 05:21:15 | Re: Bad pg_dump error message |