Re: pg_upgrade & tablespaces

It's easier to keep things segregated. It is not anymore different than
doing the upgrade in the same jail. Which at the end of the day you are
doing the upgrade in the same jail, because at the end of the day
pg_upgrade just needs the old data an binary to start and create some dump
files.

But the real problem here is with the table spaces. Because in order to
copy the relation over I would need to mount the old data to the
/usr/local/pgsql/data on the new jail. The relation would be there and
would finish successfully(I did this exercise). However the 9.3 install
would be in a different directory, say /usr/local/pgsql_93 and will not
have the data files because they now live in the old install location.

-Joseph

On Thu, Dec 19, 2013 at 3:53 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:

> On Thu, Dec 19, 2013 at 11:34:24AM -0500, Joseph Kregloh wrote:
> > Hello,
> >
> > I am trying to upgrade from 9.0.14 to 9.3. I am using the pg_upgrade
> utility. I
> > need to use pg_upgrade because my production database is 800GB+ and with
> over
> > 80 tablespaces and doing an export from 9.0 and importing to 9.3 would
> take at
> > least 2 days.
> >
> > Currently I am testing on the development database which is only 100GB
> with a
> > same number of tablespaces. I am working on FreeBSD with jails. So one
> jail
> > contains 9.0 and the other 9.3. In the 93 jail I mount the data and
> binary
> > directories for the 9.0 jail.
>
> Why don't you do run pg_upgrade in the same jail then just move the
> files over to the new jail? That should work better. I am unclear how
> a cross-jail upgrade would work at all.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + Everyone has their own god. +
>