From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | subhan alimy <salimy2011(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgresql Server Upgarde |
Date: | 2016-02-15 17:40:38 |
Message-ID: | CANu8FiyFsc9u=V6xu9ScUhEBT_wEK7+kJRvcc3GkoM5Gb1bAHg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-02-15 17:52:28 | Re: how do you determine if you have a healthy database |
Previous Message | Melvin Davidson | 2016-02-15 17:06:28 | Proper use of Groups and Users (Roles). |