Re: pgdumpall

The only problem I found using it was with a user large object type used
for OLE binary large object data.   Dumpall just dumped the OID of the
items, not the items themselves

There is a -b (dump data and BLOB data) option, if it exists on your
version of pg_dump (pg_dumpall passes most parameters through to the
pg_dump calls that it does).  I have not tried this as I am still
developing my DB and had a set of the data that could be inserted from
the front end, so just used that.

Lalo Castro wrote:
>
> Hello,
>         I suddenly am required to move databases from one server to
> another.  I have read some things on pg_dumpall and feel fairly
> confident that I can move it over with a minimum of sweat.  However,
> given the importance of  the databases to our organization and my own
> inexperience with pg_dumpall, I felt that if anyone had suggestions for
> smoothing the transition, please let me know.  If there is anything I
> should keep an eye on, or if it is not as easy as I think it will be
> (not that it ever is anyway), or if I should keep away from certain
> flags, please let me know.
>             Thanks.
>             Lalo
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org

--
This is the identity that I use for NewsGroups. Email to
this will just sit there. If you wish to email me replace
the domain with knightpiesold . co . uk (no spaces).