Thank you Stéphane.
What about the second question?
If I want to use pg_upgrade, I need to provide the -b bindir
(--old-bindir=bindir) and so my second question is what if I’ll provide
9.4 (the new PostgreSQL executable directory) also as the ‘old-bindir’, can it work that way? Always?
[I am trying to solve a problem that I might not have the old-bindir available on the machine and only the new-bindir will be available (as well as the old & new datadir of course J]
Hemy
-----Original Message-----
From: Stéphane Wirtel [mailto:stephane@xxxxxxxxx]
Sent: 20 January 2015 21:24
To: Perry, Hemy
Cc: pgsql-admin@xxxxxxxxxxxxxx
Subject: Re: [ADMIN] pg_upgrade vs. pg_dump
From: Stéphane Wirtel [mailto:stephane@xxxxxxxxx]
Sent: 20 January 2015 21:24
To: Perry, Hemy
Cc: pgsql-admin@xxxxxxxxxxxxxx
Subject: Re: [ADMIN] pg_upgrade vs. pg_dump
On 20 Jan 2015, at 20:22, Perry, Hemy wrote:
> Hello,
>
> I am planning a migration from 9.1.7 to 9.4.0.
> Based on my understanding, the recommendation is to use pg_upgrade
> over 'dump and restore'.
> Is that right?
You can compile the twice versions of PostgreSQL on the same computer and just execute the upgrade with pg_upgrade and the right parameters.
>
> If I want to use pg_upgrade, I need to provide the -b bindir
> (--old-bindir=bindir) and so my second question is what if I'll
> provide 9.4 (the new PostgreSQL executable directory) also as the
> 'old-bindir', can it work that way? Always?
> [I am trying to solve a problem that I might not have the old-bindir
> available on the machine and only the new-bindir will be available (as
> well as the old & new datadir of course :)]
>
> Thanks
> Hemy
--
Stéphane Wirtel - http://wirtel.be - @matrixise
