From: | Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Upgrade from PostgreSQL 9.6 to 11 |
Date: | 2019-06-10 07:13:06 |
Message-ID: | ae37036c-6c7c-8104-c3f8-3bdb2fcbb238@matrix.gatewaynet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/6/19 9:52 π.μ., Pawan Sharma wrote:
> Thanks all,
>
> Is pg_upgrade is the best method if I am doing upgrade on same server or different server.
>
> Same server means: source and Target on same server
>
> Different: source and Target are different server.
A traditional upgrade by definition is on the same server, (if we are not talking about logical replication or any other equivalent technology).
So yes pg_upgrade is what would be best, along with -k (--link) for maximum speed.
>
>
> On Mon, Jun 10, 2019, 12:07 PM Michael Paquier <michael(at)paquier(dot)xyz <mailto:michael(at)paquier(dot)xyz>> wrote:
>
> On Mon, Jun 10, 2019 at 09:00:38AM +0300, Achilleas Mantzios wrote:
> > On 10/6/19 7:36 π.μ., Pawan Sharma wrote:
> >> What is the best way to upgrade from PostgreSQL 9.6 to PostgreSQL
> >> 11 instead of pg_upgrade.
> >
> > why not pg_upgrade ? If the size is near the 3TB mark as you say,
> > pg_upgrade is the fastest IMHO.
>
> When it comes to upgrades, you could also look at logical
> replication. Unfortunately your origin version cannot do that. Have
> you looked at things like BDR or Slony? They are logical-based,
> meaning a lower downtime than pg_upgrade, but they take longer.
>
> For 3TB pg_upgrade can also be very fast if you use --link. Be wary
> of having backups though, all the time.
> --
> Michael
>
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2019-06-10 11:32:00 | Re: Upgrade from PostgreSQL 9.6 to 11 |
Previous Message | Pawan Sharma | 2019-06-10 06:52:09 | Re: Upgrade from PostgreSQL 9.6 to 11 |