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 1sL7vZ-00DadU-Tf for pgsql-admin@arkaria.postgresql.org; Sat, 22 Jun 2024 21:05:42 +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 1sL7vX-00FjAe-D2 for pgsql-admin@arkaria.postgresql.org; Sat, 22 Jun 2024 21:05:39 +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 1sL7vW-00Fj80-W1 for pgsql-admin@lists.postgresql.org; Sat, 22 Jun 2024 21:05:39 +0000 Received: from cc-smtpout2.netcologne.de ([2001:4dd0:100:1062:25:2:0:2]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sL7vQ-002cU4-2F for pgsql-admin@lists.postgresql.org; Sat, 22 Jun 2024 21:05:37 +0000 Received: from cc-smtpin1.netcologne.de (cc-smtpin1.netcologne.de [89.1.8.201]) by cc-smtpout2.netcologne.de (Postfix) with ESMTP id 12F8912522 for ; Sat, 22 Jun 2024 23:05:27 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netcologne.de; s=nc1116a; t=1719090327; bh=QktT5i2CgdxtnUIwEMmSqsfAXPGdEwDEhi17DpDLpRI=; h=Message-ID:Date:Subject:To:References:From:In-Reply-To:From; b=n4qLHjgZE4XUDToMg3Bg+f/yR5znx1CBjY98FkKBD8qYgZ+jh/3S1PVnJtKa/JVCv bmIe4dq7nLTeiAN33o37nR4en594zjB8HeREPXMRq2sRyrW7iIyWu9m0p7ZOWMr/y+ RNxBa64EcUkx3/mpBhrA+A4J+uhsS/Jp55xBYDou9nTxX9wt4xrLbTo9XGSElCmL9k vsPXZYvSLlQLmDz8F9GBCwU/af5BMZMDy98/O1IEm6Di7dIBeUONsV+tV7BVqPHWEC fExVphfBrKmQNzjfjGYF0tZ6YjJ1ZIFRAftq+VBU4up24UJjngjCMEESO6aCMdRmDC ka8R2Vk3cQdDA== 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-smtpin1.netcologne.de (Postfix) with ESMTPSA id DCA1011D79 for ; Sat, 22 Jun 2024 23:05:26 +0200 (CEST) Message-ID: <9832caf9-81f0-4dc6-98a8-840cb872076e@netcologne.de> Date: Sat, 22 Jun 2024 23:06:52 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Restoration To: pgsql-admin@lists.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-Queue-Id: DCA1011D79 X-Rspamd-Action: no action List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk hi, On 6/22/24 10:11 PM, Wasim Devale wrote: > Can I restore backup from barman which has postgresql 12 version's > backup to postgresql 13? Will the extension's work. Please advise or > any suggestions. without being 100% certain, I would say ...   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