Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kF1hy-0001So-SW for pgsql-admin@arkaria.postgresql.org; Sun, 06 Sep 2020 20:56:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kF1hS-0007DD-7d for pgsql-admin@arkaria.postgresql.org; Sun, 06 Sep 2020 20:55:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kF1hR-0007D5-Sn for pgsql-admin@lists.postgresql.org; Sun, 06 Sep 2020 20:55:45 +0000 Received: from mail-oi1-x243.google.com ([2607:f8b0:4864:20::243]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kF1hO-0006Ml-5s for pgsql-admin@lists.postgresql.org; Sun, 06 Sep 2020 20:55:44 +0000 Received: by mail-oi1-x243.google.com with SMTP id w16so11887746oia.2 for ; Sun, 06 Sep 2020 13:55:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=6gNOWIkj0kPA6gaf/NolD0kS0OjbBFO8qz8u61I4J6k=; b=ahWbcbcM1kfMsgeIP2AfqVxZdCXcOpUg3KjbJDEF0QtqZv2PdEU0vdvHJ1CTfqShsp LsVKjfre7efYBeRQyw/Ulyokg5uzPv9QiD/BqSNU0PSpAQY10WOW6rRlYDEja4wGLP1j p9vJL39xy6iQkd5VxE8BwfM2BofJ/+CldkeH0uLUD7OftzaY9327OwnSippBs5uZ89qN nyy+PQVQ74LJCRB8xdXX2edFe1g/oyc5WJ80C7GNhtKwmjpFNwDeMWp/ei4sxASey8I1 GzzhafpHpDKhrWC0H+6mznwZxGVK1QOzK1VxBhZnuDOU5ih7+8ADtrlAr7MQz1o2c1XV 0wJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=6gNOWIkj0kPA6gaf/NolD0kS0OjbBFO8qz8u61I4J6k=; b=trU2EGJ16qdjvvk7T6R1Bx5GhXSn4ZW6zzugL1wUs9H3szkVxSvedNS84619lMdSst gHawJVvwQH27IZ/GcSY8Y4Zc80qpRsInGrAOKKsdMqrIocZKYaX3DcyJwEdlqeF9ZZqC v5kUXBqDDwv6hA2PPM7TNmFwTe2V6iaJkPW/FahwKkRMLeujXWxHtZEWQWfiArQ2GgTL 77x15UNKLUqJrC80c+PMIvShBo2tKEWE2THB9m8aZA4KyXoQthz3uhKJdPINwS7IzVkx 3OhWD/9aXuDFEYqrv+2Yv7xWYy90UaFPN7V3uQX0d0KoJx1wF2sw9MPBrzphqfARp57h mFdg== X-Gm-Message-State: AOAM530RE+XngLYiba7roDYwwXZuC+TkgpIJnZl9b2Xc0L9fg0KzO/pZ 7j1ycMDfs25tsGjrjVwhm4vS0Nhm8L4xLQ== X-Google-Smtp-Source: ABdhPJyY6U6Sxvyo00HtiAhi4FM9bOoEYR5oD/ux5sqeBSkQE0Lj3kVKpjqYsAiE8XWTX+46zWZX0w== X-Received: by 2002:a05:6808:54:: with SMTP id v20mr10424632oic.50.1599425740840; Sun, 06 Sep 2020 13:55:40 -0700 (PDT) Received: from [192.168.1.10] (ip174-67-143-111.no.no.cox.net. [174.67.143.111]) by smtp.googlemail.com with ESMTPSA id m51sm2583442otc.26.2020.09.06.13.55.39 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 06 Sep 2020 13:55:40 -0700 (PDT) Subject: Re: Re. Postgres Upgrade. To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: <4cf6d54d-3718-a504-cb52-1053f761bb4d@gmail.com> Date: Sun, 6 Sep 2020 15:55:39 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------5D4715EEBAB78FEFD9DDB395" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------5D4715EEBAB78FEFD9DDB395 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 9/6/20 2:12 PM, Sushil Shirodkar wrote: > Hello experts, > > > Looking for advise/suggestions on the following scenario. > > Existing Setup        Moving to > > Postgres => 10.5           Postgres => 12.4 > Ubuntu   => 16.04.5     Ubuntu   => 20.04.1 > > Question: > We have new environment ready with PG 10 & PG 12 with Ubuntu 20. > > To reduce the upgrade time, can I bring the volume(10/main) from old > server to new server & connect to PG10 and do the pg_upgrade ? What about the binaries?  (Though you can install PG 10 binaries for Ubuntu 20.04 easily enough.) > will > PG10 running on "Ubuntu 16" work on "Ubuntu 20" for upgrade to PG12 ? > or I have to go thru pg_dumpall route. You could copy the volumes over and pg_upgrade, do a pg_dumpall or enable logical replication from one to another.  (That would greatly minimize downtime.) -- Angular momentum makes the world go 'round. --------------5D4715EEBAB78FEFD9DDB395 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit On 9/6/20 2:12 PM, Sushil Shirodkar wrote:
Hello experts,


Looking for advise/suggestions on the following scenario. 

Existing Setup               Moving to

Postgres => 10.5           Postgres => 12.4
Ubuntu   => 16.04.5     Ubuntu   => 20.04.1

Question:
We have new environment ready with PG 10 & PG 12 with Ubuntu 20.

To reduce the upgrade time, can I bring the volume(10/main) from old
server to new server & connect to PG10 and do the pg_upgrade ?

What about the binaries?  (Though you can install PG 10 binaries for Ubuntu 20.04 easily enough.)

will
PG10 running on "Ubuntu 16" work on "Ubuntu 20" for upgrade to PG12 ?
or I have to go thru pg_dumpall route.

You could copy the volumes over and pg_upgrade, do a pg_dumpall or enable logical replication from one to another.  (That would greatly minimize downtime.)

--
Angular momentum makes the world go 'round.
--------------5D4715EEBAB78FEFD9DDB395--