From: | Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com> |
---|---|
To: | "Perry, Hemy" <hemy_perry(at)mentor(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade vs. pg_dump |
Date: | 2015-01-21 10:37:16 |
Message-ID: | CAJghg4KYNCMSU92ZXR6pWDmHObGwohJw+nGNpGobgO05_wGg5w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Jan 20, 2015 at 5:22 PM, Perry, Hemy <hemy_perry(at)mentor(dot)com> wrote:
> Based on my understanding, the recommendation is to use pg_upgrade over
> ‘dump and restore’.
>
> Is that right?
>
>
>
pg_dump + pg_restore still works very well, but the process is generally
slower. But if you have a small database and the time it takes is not big,
then you are fine to use this method if you want to.
> 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]
>
You need both binaries in the server for pg_upgrade, there is no way around
it.
Regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres
From | Date | Subject | |
---|---|---|---|
Next Message | Harshad Adalkonda | 2015-01-21 11:15:15 | Re: pg_upgrade vs. pg_dump |
Previous Message | Perry, Hemy | 2015-01-21 10:04:58 | Re: pg_upgrade vs. pg_dump |