This change has been made. Thanks.
>
> Right, but pg_dump from 7.0 doesn't. And to upgrade from 7.0 to 7.1, you
> have to use the pg_dumpall from 7.0, not the one from 7.1. So if you
> follow the upgrade instructions in the 7.1 admin manual, the large objects
> will not be transfered.
>
> So maybe it should say:
>
> The implementations of pg_dump and pg_dumpall from versions prior to 7.1
> do not dump large objects by default. If you are upgrading from a version
> prior to 7.1 and your database uses large objects, please see the
> documentation for pg_dump and pg_dumpall for that version.
>
> thanks,
> Philip
>
> On Mon, 19 Mar 2001, Bruce Momjian wrote:
>
> > I think 7.1 does do them.
> >
> > >
> > > Hi
> > >
> > > It might be nice to add a line saying that pgdumpall doesn't do large
> > > objects to section 1.4 of admin, so that when people upgrade from 7.0 to
> > > 7.1 they don't accidentally lose their large objects. Perhaps something
> > > like:
> > >
> > > pgdumpall doesn't dump large objects by default. If your database uses
> > > large objects, please see section 8.1.4 Caveats.
> > >
> > > thanks,
> > > Philip
> > >
> > >
> > > ---------------------------(end of broadcast)---------------------------
> > > TIP 6: Have you searched our list archives?
> > >
> > > http://www.postgresql.org/search.mpl
> > >
> >
> >
> > --
> > Bruce Momjian | http://candle.pha.pa.us
> > pgman@candle.pha.pa.us | (610) 853-3000
> > + If your life is a hard drive, | 830 Blythe Avenue
> > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
> >
>
>
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026