Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iKKhA-0007Mf-FE for pgsql-admin@arkaria.postgresql.org; Tue, 15 Oct 2019 11:08:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iKKh9-0001gA-1F for pgsql-admin@arkaria.postgresql.org; Tue, 15 Oct 2019 11:08:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iKKh8-0001fl-GQ for pgsql-admin@lists.postgresql.org; Tue, 15 Oct 2019 11:08:50 +0000 Received: from mail-wr1-x42b.google.com ([2a00:1450:4864:20::42b]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iKKh5-0007As-EW for pgsql-admin@postgresql.org; Tue, 15 Oct 2019 11:08:49 +0000 Received: by mail-wr1-x42b.google.com with SMTP id z9so23311445wrl.11 for ; Tue, 15 Oct 2019 04:08:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=v0J0wfc0mySUyx+Ql1N5bcoU1fMWBAq/5+gypPbQ4QI=; b=VGJFcjicu7PY+fD0wUch7kv5QEYdU8lEfQG7UUpUl+MIYCQFitKpWv+ZTf8nSBdfzn B4S2MKXpKSBe+sI1eleS7j6Rkhf+XOzByK9L3x5ly36CKROWP3xhU02CHPNIzECIBBys ToqTmGsUqDAEBsK04RWVdBhhIplxvf3lpEUmYhp+KWxMPDGiD5snDzSmuAoWsMntoi9p ZroJ7Aw5feHoAkLJfOPsjCLHChLjOka0jPPUcSkHSJ17lz0rbFN8j8IDZFAP0oTPfIeY XP7rtPs7Ete7YTJPY2O3DzF3/X4A2WNwxGxjMbPFC3fTn/WXOHqafpkx+kNTUDbW87CK bZRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=v0J0wfc0mySUyx+Ql1N5bcoU1fMWBAq/5+gypPbQ4QI=; b=GfVlgm4+4Tl5ZxRcSUxGWmzKRGFvU1ZhLIW1N5uWahkDSNmY/Jd9Q9PvmwiOgCyS5J X+kgGkb9En/9hqkUYQ4Me/fyQZZ4SuTQrauYX5mUEIPsL0MzPYdxp005ZPMlGdRFs86z TJByTDPL8F2Qg5oQJjC8HrgesXjC9j3cxHpDTQNPn/agwbfH7PXdJikCQ9Cy4Oqj2tr4 1OBkaHVJkqIjSqBiNfKKZ3+vzNdnOhKPm5+FhybhHdidytKCuUpJJhxi4ksZEtVoiqHw lbgzqOdSfQaJBBe9Jjt2xTj/ELtv/gyEw7cGlNoR19OYPozHs8Cr3ID4HICxv4tlcu0z my6g== X-Gm-Message-State: APjAAAVf34SV/4rU4zMG+BHfqSHPJgU4EHLdgVk2kKZRQk+hEf6UDHoG RrkL/W/iV898Jqo1AqSImZaLLQ== X-Google-Smtp-Source: APXvYqzR6lqH1B3XklixRtMDjnPF5aLOE7aF0lO96GU4NNsFeaCg+BjJ6yJSZ3AggDjDMv6vd+sG1w== X-Received: by 2002:a5d:43c1:: with SMTP id v1mr30994774wrr.91.1571137724900; Tue, 15 Oct 2019 04:08:44 -0700 (PDT) Received: from localhost.localdomain (217-149-169-173.nat.highway.telekom.at. [217.149.169.173]) by smtp.gmail.com with ESMTPSA id r20sm29020550wrg.61.2019.10.15.04.08.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 15 Oct 2019 04:08:44 -0700 (PDT) Message-ID: <1ce68bf19e4bbbf2195c5a2e5671406e4b3253ba.camel@cybertec.at> Subject: Re: pg_upgradecluster with --link from 9.6 to 12 From: Laurenz Albe To: Wells Oliver , pgsql-admin Date: Tue, 15 Oct 2019 13:08:43 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.4 (3.32.4-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Wells Oliver wrote: > Is this alright to do, or do I need to go from 9.6 to 10 to 11 to 12? You can directly upgrade from 9.6 to 12 using "pg_upgrade", which is used under the hood by "pg_upgradecluster". Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com