From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
---|---|
To: | John Madden <jmadden(at)ivytech(dot)edu> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: pg_dumpall and output formats? |
Date: | 2002-08-19 20:46:18 |
Message-ID: | 1029789978.9771.74.camel@camel |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
*pg_dumpall* doesn't support large objects
pg_dumpall [-c | --clean] [-g | --globals-only] [-h host] [-p port] [-U
username] [-W]
But note a limitation: it cannot dump "large objects", since pg_dump
cannot dump such objects into text files. If you have databases
containing large objects, they should be dumped using one of pg_dump's
non-text output modes.
http://www.postgresql.org/idocs/index.php?app-pg-dumpall.html
You'll need to dump that db explicitly with pg_dump.
Robert Treat
On Mon, 2002-08-19 at 12:16, John Madden wrote:
> When trying to dump all of our databases,
>
>
> pg_dumpall -b -o -F t --f full_pgbackup.tar
>
>
> We're getting:
>
>
> pg_dump: large object output is not supported for plain text dump files.
> pg_dump: (Use a different output format.)
>
>
> So it would seem that the "-F t" isn't getting passed to pg_dump. The
> option set does work fine when using pg_dump alone on a single database.
> What am I doing wrong here?
>
> Thanks,
> John
>
>
>
>
>
> --
> John Madden
> UNIX Systems Engineer
> Ivy Tech State College
> jmadden(at)ivytech(dot)edu
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
From | Date | Subject | |
---|---|---|---|
Next Message | John Madden | 2002-08-19 20:54:52 | Re: pg_dumpall and output formats? |
Previous Message | Tom Lane | 2002-08-19 20:42:58 | Re: Limits to size of shared buffers? |