Thread: pg_upgrade 9.1.9 ->9.3.1

pg_upgrade 9.1.9 ->9.3.1

From
Marc Mamin
Date:
Hello,

I'm evaluating pg_upgrade and there seems to be something wrong with my test:
the data get copied within the old data directory instead of the new one

Do I have to explicitely set more option or define some environment variables ?

If this is of concern, there are some redirections with symlinks within the old $PGDATA


./pg_upgrade \
 --old-datadir "/data/postgresql-data-9"\
 --new-datadir "/pgdata/postgresql_93-data-9"\
 --old-bindir "/opt/intershop/postgresql-9.1.9-9/bin"\
 --new-bindir "/opt/intershop/postgresql-9.3.1-9/bin"

=>

ll /data/postgresql-data-9/tblspc_data/cicpg_logs/

drwx------ 3 isdb9 isgrp9 4096 Oct 21 15:48 PG_9.1_201105231
drwx------ 3 isdb9 isgrp9 4096 Oct 25 12:26 PG_9.3_201306121


thanks,

Marc Mamin


Re: pg_upgrade 9.1.9 ->9.3.1

From
Peter Eisentraut
Date:
On 10/25/13, 7:20 AM, Marc Mamin wrote:
> Hello,
>
> I'm evaluating pg_upgrade and there seems to be something wrong with my test:
> the data get copied within the old data directory instead of the new one
>
> Do I have to explicitely set more option or define some environment variables ?
>
> If this is of concern, there are some redirections with symlinks within the old $PGDATA
>
>
> ./pg_upgrade \
>  --old-datadir "/data/postgresql-data-9"\
>  --new-datadir "/pgdata/postgresql_93-data-9"\
>  --old-bindir "/opt/intershop/postgresql-9.1.9-9/bin"\
>  --new-bindir "/opt/intershop/postgresql-9.3.1-9/bin"
>
> =>
>
> ll /data/postgresql-data-9/tblspc_data/cicpg_logs/
>
> drwx------ 3 isdb9 isgrp9 4096 Oct 21 15:48 PG_9.1_201105231
> drwx------ 3 isdb9 isgrp9 4096 Oct 25 12:26 PG_9.3_201306121

It appears you are using tablespaces.  In that case, that's normal.



Re: pg_upgrade 9.1.9 ->9.3.1

From
Marc Mamin
Date:
> From: Peter Eisentraut [mailto:peter_e@gmx.net]


> On 10/25/13, 7:20 AM, Marc Mamin wrote:
> > Hello,
> >
> > I'm evaluating pg_upgrade and there seems to be something wrong with
> my test:
> > the data get copied within the old data directory instead of the new
> > one
> >
> > Do I have to explicitely set more option or define some environment
> variables ?
> >
> > If this is of concern, there are some redirections with symlinks
> > within the old $PGDATA
> >
> >
> > ./pg_upgrade \
> >  --old-datadir "/data/postgresql-data-9"\  --new-datadir
> > "/pgdata/postgresql_93-data-9"\  --old-bindir
> > "/opt/intershop/postgresql-9.1.9-9/bin"\
> >  --new-bindir "/opt/intershop/postgresql-9.3.1-9/bin"
> >
> > =>
> >
> > ll /data/postgresql-data-9/tblspc_data/cicpg_logs/
> >
> > drwx------ 3 isdb9 isgrp9 4096 Oct 21 15:48 PG_9.1_201105231
> > drwx------ 3 isdb9 isgrp9 4096 Oct 25 12:26 PG_9.3_201306121


> It appears you are using tablespaces.  In that case, that's normal.

which means I cannot take advantage of a separate new file system for the copy and first have to organize enough free
placein the "old" one. 
correct ?

thanks,

Marc