Re: Postgresql Server Upgarde

From: Felipe Santos <felipepts(at)gmail(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>
Cc: subhan alimy <salimy2011(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgresql Server Upgarde
Date: 2016-02-15 18:00:04
Message-ID: CAPYcRiU4N7QMzFUmXZSoEKC2eLRdQY4Dq77mT0CJN64HCWSTeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2016-02-15 15:40 GMT-02:00 Melvin Davidson <melvin6925(at)gmail(dot)com>:

>
>
> On Tue, Feb 9, 2016 at 1:57 AM, subhan alimy <salimy2011(at)gmail(dot)com> wrote:
>
>> Hello Everyone,
>>
>> I want to upgrade PostgreSQL 9.1 to PostgreSQL 9.4, currently my database
>> hold millions of records, shall anyone please help me the recommend steps
>> to
>> upgrade my servers without any technical impact.
>>
>> Thanks In Advance.
>>
>> --
>> View this message in context:
>> http://postgresql.nabble.com/Postgresql-Server-Upgarde-tp5886543.html
>> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>>
>>
>> --
>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>> To make changes to your subscription:
>> http://www.postgresql.org/mailpref/pgsql-general
>>
>
>
> Please refer to the following documentation:
>
> http://www.postgresql.org/docs/9.4/static/pgupgrade.html
>
> CAVEAT EMPTOR: It is always advisable to have a valid pg_dump/backup
> before proceeding with pg_upgrade.
> pg_upgrade is faster than a reload, but in the event of unexplained
> problems, a backup is always good to have as a last resort.
> Also, practice upgrading in a development environment before attempting to
> do so in production.
>
> --
> *Melvin Davidson*
> I reserve the right to fantasize. Whether or not you
> wish to share my fantasy is entirely up to you.
>

Hi Subhan Alimy,

I would recommend that, in an environment apart from production (maybe your
DEV env), you should:

1. install PG 9.4 in a different dir than PG 9.1
2. create a new cluster, apart from dev/test/qa/etc in a new data dir
3. do a dump from the PG 9.1 cluster
4. restore the dump to the PG 9.4 cluster
5. test your application on the new cluster

Given that you have enough storage space on the production environment, you
could use the same approach to upgrade your prod database.

Regards,

Felipe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Travers 2016-02-15 19:22:11 Suggest note in index documentation about long running transactions
Previous Message Adrian Klaver 2016-02-15 17:59:19 Re: Manage SCD 2 table using the INSERT --- ON CONFLICT