| From: | Lonni J Friedman <netllama(at)gmail(dot)com> |
|---|---|
| To: | Igor Neyman <ineyman(at)perceptron(dot)com> |
| Cc: | AI Rumman <rummandba(at)gmail(dot)com>, Fabio Rueda Carrascosa <avances123(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade link mode |
| Date: | 2013-05-16 18:23:27 |
| Message-ID: | CAP=oouGHP=CQmH=W4Cs4LP3gtyizN_EqyLJ-CtywV1ywfSRNwg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 16, 2013 at 11:03 AM, Igor Neyman <ineyman(at)perceptron(dot)com> wrote:
>
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)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?
I assume what he's referring to is if the upgrade gets partially
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AI Rumman | 2013-05-16 18:27:03 | Re: pg_upgrade link mode |
| Previous Message | AI Rumman | 2013-05-16 18:21:16 | Re: pg_upgrade link mode |