Re: pg_upgrade link mode

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: AI Rumman <rummandba(at)gmail(dot)com>
Cc: Igor Neyman <ineyman(at)perceptron(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-21 21:16:28
Message-ID: 20130521211628.GE1322@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 16, 2013 at 02:21:16PM -0400, AI Rumman wrote:
> I told you I would never go for a production with link mode. However, I was
> working with pg_upgrade copy mode and in the middle I got an error saying
> missing some extensions. I rollback and start the operation after setting
> everything up.
> I don't know how it will behave in link mode if you fail in the middle.

I guess a lot of people prefer to guess about the risks of --link mode
rather than read the pg_upgrade manual, which says:

http://www.postgresql.org/docs/9.3/static/pgupgrade.html

If you use link mode, the upgrade will be much faster (no file copying),
but you will not be able to access your old cluster once you start the
new cluster after the upgrade. Link mode also requires that the old and
new cluster data directories be in the same file system. See pg_upgrade
--help for a full list of options.

So, no, you don't get a mess if the upgrade fails in the middle, even in
link mode, but you would be in trouble if you started the new server and
wanted to revert to the old server.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Browse pgsql-general by date

  From Date Subject
Next Message fburgess 2013-05-21 21:53:45 Very slow inner join query Unacceptable latency.
Previous Message Dev Kumkar 2013-05-21 20:59:24 Re: [GENERAL] ODBC constructs