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 1lov1l-00063U-Mw for pgsql-general@arkaria.postgresql.org; Thu, 03 Jun 2021 21:37:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lov1k-0007Qi-MX for pgsql-general@arkaria.postgresql.org; Thu, 03 Jun 2021 21:37:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lov1k-0007Qa-Dg for pgsql-general@lists.postgresql.org; Thu, 03 Jun 2021 21:37:20 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lov1i-0007mX-9o for pgsql-general@lists.postgresql.org; Thu, 03 Jun 2021 21:37:19 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 8613D5C0220; Thu, 3 Jun 2021 17:37:17 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 03 Jun 2021 17:37:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= subject:to:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=O Nu2jP5SzZNpwGcVxIpEBOvwGNNdeI+h3sG/8LsqZjU=; b=bvlwIu5Qpi7EE3tAt wdHSLXPi7d1CBydd0LCjebyjP1ESbAW3Sj5LTnnyu88xJTP+MRg6g/H6Ac3iCdrI oXvS6JomrOhFxXlyUNcPtSa+9qiaOkZ3yYSEHGUHv0RyWhG/uSQBqVz5iQQ0mkFs 2ezrivRJ20t9MdBHbgkFuigIQgwgE8n5FpE7lq7t5GEoOkGQ+NZoz7/Qf6XHwKpM 0RoG0MFsZc+9q+w2pbkAzc2z1f/Gk82makYD6UzIwrjd75Arn3n3VXFhW52+C2Oy oYUOX5vqsz/WWhIQmNP/F8WKcVPIZ9yjaUSTuDsAYQ6Cf2ajglrtHQKaHwlAD2et rCrwg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=ONu2jP5SzZNpwGcVxIpEBOvwGNNdeI+h3sG/8LsqZ jU=; b=HG4Xg9kGOoDTpl3w3g6moAuNioqHfgSId1Jv7CfwkAySTgCSk+KM0o/iy nLatGEX8QNK/bo0dRwy0o4RuNgIm0FA0/PSKOM3pGvXYtHGjEw1RF4VvosV2YQIc k4fr1bGOABhUs/EhK1sjv3DF4txODmepLV30mjw47dXr9mUauqyAwH00D76b+2Ta Z+ksFaIId40wa4Fasod8qSRVEl3E4W2mwvLhzafvU3USuuNTi9KGx+j2H+JNzhYc Nk4PSGaZkb0GH7Oxoq0NeLRA2CvOv8DjW49imDzBiNRMUQsIfsInsQmqw+WXCbcV NnA9a86pmwCOhKoVENjsxobQvfaUw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdelledgudeifecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefuvfhfhffkffgfgggjtgfgsehtjeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepveetjedtieekteefhffhhfetledvkeffvedugeej ueekhffgvdeileeitdekvefhnecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughr ihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 3 Jun 2021 17:37:16 -0400 (EDT) Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version To: Ram Pratap Maurya , "pgsql-general@lists.postgresql.org" References: <17046-653f73611eea8857@postgresql.org> From: Adrian Klaver Message-ID: <0ff2f400-b8ac-c2cd-68a5-702a096c019d@aklaver.com> Date: Thu, 3 Jun 2021 14:37:16 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 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/3/21 5:53 AM, Ram Pratap Maurya wrote: > Hi Team, > > I am creating new server and installed postgres -13 and take PG_BACKUP form current PRD server (PG version 11) and restore DB on PG-13 server. > can you suggest if we doing upgrade by this activity there is any issue. When doing this you should use the later version(13) of pg_dump to dump the earlier version, are you doing that? If you are then you have eliminated one possible issue. You should also read the Release Notes section of version 12 and 13: https://www.postgresql.org/docs/12/release.html https://www.postgresql.org/docs/13/release.html to see what things have changed that may affect your current set up. > > > > Regards, > Ram Pratap. > > -----Original Message----- > From: David Rowley [mailto:dgrowleyml@gmail.com] > Sent: 03 June 2021 18:01 > To: Ram Pratap Maurya; PostgreSQL mailing lists > Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version > > On Fri, 4 Jun 2021 at 00:22, PG Bug reporting form wrote: >> i am creating new server and installed postgres -13 and take PG_BACKUP >> form current PRD server (PG version 11) and restore DB on PG-13 >> server. can you suggest if we doing upgrade by this activity there is any issue. > > The form you've used is for reporting bugs yet, this does not seem to be a bug report. > > If you're looking for general help and advice then you should consider asking on one of the mailing lists. > > https://www.postgresql.org/list/ > > pgsql-general might be the best fit. > > David > -- Adrian Klaver adrian.klaver@aklaver.com