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 1lpAkN-0008Qs-Fc for pgsql-general@arkaria.postgresql.org; Fri, 04 Jun 2021 14:24:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lpAkM-0000H5-9v for pgsql-general@arkaria.postgresql.org; Fri, 04 Jun 2021 14:24:26 +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 1lpAkK-0000Gw-Th for pgsql-general@lists.postgresql.org; Fri, 04 Jun 2021 14:24:26 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lpAkC-0007yZ-VQ for pgsql-general@lists.postgresql.org; Fri, 04 Jun 2021 14:24:24 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DD26D5C0150; Fri, 4 Jun 2021 10:24:13 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 04 Jun 2021 10:24:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=9 lFIPjTNCPoco9K4FkB9Ujh8VYltiLFX1NYq49W2mq8=; b=ogQGyQa04qBK2PUI2 bTamP6gkVT7CNRgsKAHQvs6ku38n/IxLuJ+Z+UjDGrnLtdGdFx0vIu9HTDQeu5CK 3o/NhT78hvf0+NVxFJ9MLepxwXp7YK6QKY/FKixFtBP1NGn46PTiAbrpQfzQ9iun Zu8IC3OCrWax2YqZ7mDJMTj5sodSjodSkcNXN0kt1Ix+6pOMeCUnCnY0UBtBeNkZ EiPz97thbbGe2ewp6K8rayFTIHZCDzI9R8i4pfLF2qwtPXYHhrHeruINoNqU1GK0 o3PZ3zoSiKl2Ilcx+jAGGwKKfXfszWUbg1iQ8RzSbybhUyP/jU8piXsP97/h4Crm gDzHQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=9lFIPjTNCPoco9K4FkB9Ujh8VYltiLFX1NYq49W2m q8=; b=F3vD0CmM3ScID0QhxD+nqyouBGwXXeRZFPRQVQSrH0NcTjfuOGIbPHCHj OlOi7M6eGo1QK08gp2vKaXgKvSpz7z50CjUr/Nvg7t58lsaq5oORBAyznNrxW8Y2 C0oZLfYnpQcHeej6Xoy4ZYavu7worAXjBDXNT4B1JTjqOeP+d8y9xReT74UMoN0B 61Hbnu6DICzdQicyGmSUCQebI8UBrOu952SSkTDrj43jOJxmIqlzdtHIUh8eGqJI Jkwxw7fVoH+2QEJFDDP+0OghQgNx1rEljTK0MPac+8ITqWa6Yg67PnhZjUlOrkQr hjg00qFKrPvFTmvXAmki01XG+y72g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfedtuddgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthejredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeevteejtdeikeetfefhhffhteelvdekffevudegjeeu kefhgfdvieeliedtkeevhfenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 4 Jun 2021 10:24:12 -0400 (EDT) Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version To: Ram Pratap Maurya , "pgsql-general@lists.postgresql.org" Cc: Ashish Chugh References: <17046-653f73611eea8857@postgresql.org> <0ff2f400-b8ac-c2cd-68a5-702a096c019d@aklaver.com> From: Adrian Klaver Message-ID: <45165dc6-cb05-3b67-b06e-c14ddaea5560@aklaver.com> Date: Fri, 4 Jun 2021 07:24:12 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 6/4/21 4:46 AM, Ram Pratap Maurya wrote: > Dear Adrian, > Please do not top post. It is the convention on this list to post inline or bottom post. > Currently I am using postgres 11 version and I want to upgrade postgres 13 and I am doing this activity , first we take pgbase_backup from from Postgres 11 and restore this backup on postgres 13 (new server). Which version of pg_basebackup are you using to take backup of 11 version? See here: https://www.postgresql.org/docs/13/app-pgbasebackup.html "pg_basebackup works with servers of the same or an older major version, down to 9.1." What is the exact command you are using? > I am not using pg_dump . > I have done this activity on test server and its is working fine . > My confusion is it is possible to in future we face any issue like upgrade and vacume or we can`t use all added new feature in postgres 13. You will still need to VACUUM, though AUTOVACUUM should take care of that. Not sure what you mean about upgrade? The new features will be available to you. > > > > > Regards, > Ram Pratap. > > -----Original Message----- -- Adrian Klaver adrian.klaver@aklaver.com