Re: Major upgrade of PostgreSQL and MySQL

From: Igor Neyman <ineyman(at)perceptron(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>, Patrick Dung <patrick_dkt(at)yahoo(dot)com(dot)hk>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Ivan Voras <ivoras(at)freebsd(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Major upgrade of PostgreSQL and MySQL
Date: 2013-09-13 18:14:35
Message-ID: A76B25F2823E954C9E45E32FA49D70EC4281B91B@mail.corp.perceptron.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-
> owner(at)postgresql(dot)org] On Behalf Of Stephen Frost
> Sent: Friday, September 13, 2013 2:06 PM
> To: Patrick Dung
> Cc: pgsql-general(at)postgresql(dot)org; Ivan Voras; Tom Lane
> Subject: Re: [GENERAL] Major upgrade of PostgreSQL and MySQL
>
>
> > 3. But the way, if users is using Windows, is the link option still works?
>
> Don't think so, but not sure. pg_upgrade could be made to work in a truely
> "in-place" method if there's demand for it and someone wants to work on it.
> It'd clearly be a bit more *dangerous*, of course..
>
> Thanks,
>
> Stephen

Like I said in the other message, actually in-place upgrade using symbolic links work quite fine under Windows.
I tested it carefully many times, and used it even more upgrading production systems.
I don't feel it's *dangerous*, especially considering that my whole upgrade process always starts with backing up existing cluster.

Regards,
Igor Neyman

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message NWRFC Portland 2013-09-13 18:32:47 Postgres 9.2.4 "Double Precision" Precision
Previous Message Stephen Frost 2013-09-13 18:05:46 Re: Major upgrade of PostgreSQL and MySQL