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 1tNJtt-00AA8U-1M for pgsql-general@arkaria.postgresql.org; Mon, 16 Dec 2024 22:49: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 1tNJtq-00C8On-IT for pgsql-general@arkaria.postgresql.org; Mon, 16 Dec 2024 22:49:15 +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 1tNJtq-00C8Nz-7q for pgsql-general@lists.postgresql.org; Mon, 16 Dec 2024 22:49:15 +0000 Received: from fhigh-a1-smtp.messagingengine.com ([103.168.172.152]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tNJto-003C3Z-N4 for pgsql-general@postgresql.org; Mon, 16 Dec 2024 22:49:14 +0000 Received: from phl-compute-04.internal (phl-compute-04.phl.internal [10.202.2.44]) by mailfhigh.phl.internal (Postfix) with ESMTP id 7F2241140227; Mon, 16 Dec 2024 17:49:11 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-04.internal (MEProxy); Mon, 16 Dec 2024 17:49:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1734389351; x=1734475751; bh=u+h9ugJj/5YraGW+GG6545x9lKiuh+yT89C7LlUgGTA=; b= X7oAf74cBAy43xRbDhar9fm3vrtopk+CoBS9npJVK/DxYjuwTUKBkLIUuiZlPgRW AdqyMPwRwJEQLKd1h5h+ObHCzbS5RyMvNHQHxVoMLHwUPkn7zXA9rtfFFJh/EH8G StHkpacREIGhW/jyhhq4eLosxTY9OFgrZ1oaWuWfOvrGsZhUx7CZ5FYX5qihJpQL 10ZGeQmPm6cFhlUtJGoEzmQK37dN+/wLNMV4dK2GXaWJPXQoMdg1u8qm4PYzplzB dJePDuxfKeMJZ7UaOZDGI9mxUukyLxW1rc+BH+JuKvIyxgE64GrpfyFGBLqhyf2S EYnrLy9QtJ+ar/FpmjBn7Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1734389351; x=1734475751; bh=u +h9ugJj/5YraGW+GG6545x9lKiuh+yT89C7LlUgGTA=; b=Iz96sYJZf4de+nbfo DaPvR8+Bp2MUcrNQteJbdX5LaI+92tj6YnB/et8tfqIBouBo2Q2CdYZ5fqDX7q7t 3zzixy+Ir0g7kqKUyGtVGaXVK0OVzSpmYSX6g2JtzfiJENnMkdkk3JmPNH7v2nM0 VAcHshLsW/Xcd61rp5Z3RfKBraunsN1w2wvw0SlGstOWEVQwI4Mcg/H+DCy+bVAG /phvE6SgZsqCvCRSJ/jw+XRS6u8vo4msArN+L6fQrcdJ8QEoh+owaNaiXI3chS0w Di9/VgMbIPTK8P0uwwYq7HQ2KX3k0Lba7R+s9KO7UZ+Jb5D3hGtEOpxea6o6wRJG Y9gOw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrleeggddtfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtvdejnecu hfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrg hklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepffelgeeifefgveduhedthfek uedtffejveegffegjeevtdehgfduieetfeehjeehnecuvehluhhsthgvrhfuihiivgeptd enucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgr vhgvrhdrtghomhdpnhgspghrtghpthhtohepfedpmhhouggvpehsmhhtphhouhhtpdhrtg hpthhtohepvghsthgvvghmsghsvhdqfhhorhhumheshigrhhhoohdrtghomhdprhgtphht thhopehrohhnlhhjohhhnhhsohhnjhhrsehgmhgrihhlrdgtohhmpdhrtghpthhtohepph hgshhqlhdqghgvnhgvrhgrlhesphhoshhtghhrvghsqhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 16 Dec 2024 17:49:10 -0500 (EST) Message-ID: Date: Mon, 16 Dec 2024 14:49:10 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Additional Help in vetting my steps for Postgres DB upgrade from Ver 13.X to ver 15.X To: Bharani SV-forum , Ron Johnson , pgsql-general References: <0558ddd4d71641bdb41fa49b2425f73c@safrangroup.com> <98965993.3138805.1731699978332@mail.yahoo.com> <564950518.5117550.1733177884387@mail.yahoo.com> <07ab2d83-ffe5-4bec-9626-22a68f732579@aklaver.com> <273a88dc-4134-47d5-bc19-30ff5f97926c@aklaver.com> <498dfb34-4dd7-4f48-8188-355e1488d7e6@aklaver.com> <1061066336.5835157.1733316137292@mail.yahoo.com> <1918413683.2239751.1733944364448@mail.yahoo.com> <037a8338-3434-47d4-aaad-ef186d4d3250@aklaver.com> <101139100.4053671.1734383960480@mail.yahoo.com> <1875422740.4095620.1734388259706@mail.yahoo.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: <1875422740.4095620.1734388259706@mail.yahoo.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 12/16/24 14:30, Bharani SV-forum wrote: > *a) * > *user = * > postgres > > b) > *pg_dump version = * > /usr/bin/pg_dump -V > > pg_dump (PostgreSQL) 13.16 > > c) > > *DB version* > > select version () ; >                                                  version > ---------------------------------------------------------------------------------------------------------- >  PostgreSQL 13.16 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 > 20150623 (Red Hat 4.8.5-44), 64-bit > > *use this script for backup* > > pg_dump -Fp -p 5432 -U "$USERNAME" "$DATABASE" > > using username = postgres > > for one of the DB (ver 13.16), it worked fine by doing oldvm = pg_dump > from ver 13.16 and > later restoring in new VM with new OS and new db binary 15.09, post > creating dummy db (appln related) and restoring the pg_dump from oldvm . > That's nice, but the issue is the case that did not work. What process where you running that caused the error? -- Adrian Klaver adrian.klaver@aklaver.com