Re: pg_upgrade link mode
От | AI Rumman |
---|---|
Тема | Re: pg_upgrade link mode |
Дата | |
Msg-id | CAGoODpeyuDzokJV9Z=3vbjzQRVQ-sXPuPwpo+Ly0o3Ycmqttuw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_upgrade link mode (Lonni J Friedman <netllama@gmail.com>) |
Список | pgsql-general |
Yes Lonni. I agree with you.
On Thu, May 16, 2013 at 2:23 PM, Lonni J Friedman <netllama@gmail.com> wrote:
I assume what he's referring to is if the upgrade gets partiallyOn Thu, May 16, 2013 at 11:03 AM, Igor Neyman <ineyman@perceptron.com> wrote:
>
> From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of AI Rumman
> Sent: Thursday, May 16, 2013 1:56 PM
> To: Fabio Rueda Carrascosa
> Cc: pgsql-general
> Subject: Re: [GENERAL] pg_upgrade link mode
>
> I always think its a bit risky to use link instead of copying. However, I'd suggest to try the --check at first of pg_upgrade.
>
> --------------------------------------------------------------
>
> Why?
> Do you have specific experience, when link mode caused any problems?
> Could you share?
completed and fails for any reason, then you have a broken mess, with
no simple rollback path. Since your database is only about 1GB in
size, it shouldn't take very long to run a base backup before doing
the upgrade. You can send that backup over the network to a remote
system, so that you have a fallback solution if the upgrade fails.
В списке pgsql-general по дате отправления: