Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sLKer-00EPSg-03 for pgsql-admin@arkaria.postgresql.org; Sun, 23 Jun 2024 10:41:17 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sLKen-0092PA-KA for pgsql-admin@arkaria.postgresql.org; Sun, 23 Jun 2024 10:41:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sLKen-0092P2-6P for pgsql-admin@lists.postgresql.org; Sun, 23 Jun 2024 10:41:13 +0000 Received: from cc-smtpout3.netcologne.de ([2001:4dd0:100:1062:25:2:0:3]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sLKej-002hzE-Q9 for pgsql-admin@postgresql.org; Sun, 23 Jun 2024 10:41:12 +0000 Received: from cc-smtpin2.netcologne.de (cc-smtpin2.netcologne.de [89.1.8.202]) by cc-smtpout3.netcologne.de (Postfix) with ESMTP id A963F1220A; Sun, 23 Jun 2024 12:41:04 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1719139264; bh=v33SQ2ociPQueKXBgTtF0JNnbd1gyhdKFv50uy6g6R0=; h=Message-ID:Date:Subject:To:Cc:References:From:In-Reply-To:From; b=haJzdWNOk73xXr+ssUmdd4sxDBXrBV7eDp8aP2pNFPHlyYxPa3+UZwcg1RbLSaYFb D5Uo6IHjxUUYCp3SxPGqP0NZkFoWZG9Ec4l7bLOtcQkmpTnER7XO7L1iJw4/wzd6Xm dOEVRTRy0MuYvpXDlZ9cauQdqtv0qhKGF8dhlg1d8xCnfc1j46+rBEPeDzAGgyAeso Aho3LOKRUbwVdl/O+VnQR/q9MCJZwG18edeQGwiMtO7QneyD81D4yAi8wHge4eqiCd ezUC2lQis5qqosXwF7O3e86NphiVaM9RCqUMQFqK17qEza8H+3Jwhmkt3tV3xakd61 8zC7c+gHZ0Nzw== Received: from [IPV6:2a03:b580:aaca:7d01:476f:3f7b:3545:419a] (unknown [IPv6:2a03:b580:aaca:7d01:476f:3f7b:3545:419a]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by cc-smtpin2.netcologne.de (Postfix) with ESMTPSA id 2DAEF11E24; Sun, 23 Jun 2024 12:41:03 +0200 (CEST) Message-ID: <644e1420-829e-4ac4-80b2-650688c91685@netcologne.de> Date: Sun, 23 Jun 2024 12:42:28 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Restoration To: Wasim Devale Cc: pgsql-admin@postgresql.org References: Content-Language: en-US From: vrms In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-NetCologne-Spam: L X-Spamd-Bar: - X-Rspamd-Action: no action X-Rspamd-Queue-Id: 2DAEF11E24 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 6/23/24 12:02 PM, Wasim Devale wrote: > > So I can work with the minor version upgrade. I can restore postgresql > 12.8 backup from barman to postgresql 12.19 I hope I will get it done. > Thanks > not sure whether my last response came through >>  1. barman creates a physical copy of the data directory >>  2. the data directory does work for the version it was created with via initdb            so you can not just run your pg12 restore on a pg13 instance >>  3. restoring the data directory plus running pg_upgrade should do the job though so #3 would be the thing I'd try    - restore the backup from v12 to a temporary directory into your server runnig v12 AND v13    - run pg_upgrade if you don't know how that works in detail let us know regards Gunnar