On Thu, May 16, 2013 at 11:03 AM, Igor Neyman <iney...@perceptron.com> wrote: > > From: pgsql-general-ow...@postgresql.org > [mailto:pgsql-general-ow...@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?
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. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
