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 1nKJC2-0007ES-3u for pgsql-admin@arkaria.postgresql.org; Wed, 16 Feb 2022 12:13:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nKJC1-00024r-3u for pgsql-admin@arkaria.postgresql.org; Wed, 16 Feb 2022 12:13:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKJC0-00024h-Nb for pgsql-admin@lists.postgresql.org; Wed, 16 Feb 2022 12:13:56 +0000 Received: from mail.pscs.co.uk ([178.159.9.185]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nKJBy-0007CO-ML for pgsql-admin@lists.postgresql.org; Wed, 16 Feb 2022 12:13:56 +0000 Authentication-Results: mail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=pscs Received: from lmail.pscs.co.uk ([192.168.150.1]) by mail.pscs.co.uk ([192.168.150.185] running VPOP3) with ESMTPSA (TLSv1.3 TLS_AES_256_GCM_SHA384) for ; Wed, 16 Feb 2022 12:13:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pscs.co.uk; q=dns/txt; s=lmail; h=Message-ID:Date:MIME-Version:Subject:To:References:From:In-Reply-To :Content-Type:Content-Transfer-Encoding:Cc:Reply-to:Sender; t=1645013297; x=1645618097; bh=4i1g53a89I9g2r/rULWYaurstxA1ZkaQ/uam/lJBVYw=; b=a+t649rnBWp/G/RXHPe8kI1qCAjdVwlyUaSo0rEMVnfR8szNIlD27rv3u2DwM7+vWxGNdfQJ Wkp2xleO6RtrqbQYJaN1j5xqX6U87TpTQi/UoIW3fs08ZvE5eMUwHldCxvEAHl67le0JFoVvr9 ZiB4RnvApCFOmwat/7ueXu3v4= Authentication-Results: lmail.pscs.co.uk; spf=none; auth=pass (cram-md5) smtp.auth=paul Received: from [192.168.57.78] ([82.68.48.206] (82-68-48-206.dsl.in-addr.zen.co.uk)) by lmail.pscs.co.uk ([192.168.150.70] running VPOP3) with ESMTPSA (TLSv1.3 TLS_AES_256_GCM_SHA384) for ; Wed, 16 Feb 2022 12:08:17 -0000 Message-ID: <3608d5cd-5d62-473f-0c09-20973b0e9a52@pscs.co.uk> Date: Wed, 16 Feb 2022 12:08:14 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 Subject: Re: Differential backup in database migration To: pgsql-admin@lists.postgresql.org References: From: Paul Smith In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Authenticated-Sender: paul X-Server: VPOP3 Enterprise V8.3 - Registered X-Organisation: Paul Smith Computer Services X-VPOP3Tester: 12 345 X-Authenticated-Sender: pscs List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 16/02/2022 11:24, Alex Balashov wrote: > I’m faced with the daunting prospect of upgrading a PG 9.6 installation to 14, in the process migrating a ~400 GB database. Due to the large jump in major versions, the on-disk block storage of course will not be in the slightest bit binary-compatible, How do you know it will not be binary compatible? I'm fairly sure I've upgraded 9.5 to 14 using pg_upgrade... If you use the 'link' option in pg_upgrade it just takes a few minutes with databases that big. I'd take a backup, put it on a test machine with 9.5 and try to upgrade it. You may be pleasantly surprised Paul -- Paul Smith Computer Services Tel: 01484 855800 Vat No: GB 685 6987 53 Sign up for news & updates at http://www.pscs.co.uk/go/subscribe