Re: Postgres UPGRADE from 9.2 to 9.4

From: Venkata B Nagothi <nag1010(at)gmail(dot)com>
To: Patrick B <patrickbakerbr(at)gmail(dot)com>
Cc: John R Pierce <pierce(at)hogranch(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Postgres UPGRADE from 9.2 to 9.4
Date: 2016-09-07 03:21:57
Message-ID: CAEyp7J8+oNNePKMNQtST-5Dh9dypENM+pmxnd+ntffcNHU34+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Sep 7, 2016 at 10:43 AM, Patrick B <patrickbakerbr(at)gmail(dot)com> wrote:

>
>> how large is the full database cluster?
>>
>> if its only a few GB or whatever, and not grossly complex, pg_dumpall -h
>> oldhost | psql -h newhost, is the simplest way to move a complete set of
>> databases from an old server to a new. if there are large tables with
>> millions of rows indexed, make sure you set maintenance_work_mem on the new
>> server to 2GB before running this.
>>
>>
>> it's a full copy from the production, so it's 2.3TB
>

Thats quite huge. pg_upgrade would be a better choice and yes, downtime is
needed. You need to have the database shutdown all through the upgrade
process.

How long it will take depends on type of Disks you have. It is definitely a
lot faster than pg_dump/pg_restore.

Regards,
Venkata B N

Fujitsu Australia

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2016-09-07 03:53:05 Re: Postgres UPGRADE from 9.2 to 9.4
Previous Message Nguyễn Trần Quốc Vinh 2016-09-07 02:47:33 Re: Materialized view auto refresh