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 1ou5a7-0005Rp-Vq for pgsql-general@arkaria.postgresql.org; Sun, 13 Nov 2022 05:31:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ou5a5-0007Yv-0z for pgsql-general@arkaria.postgresql.org; Sun, 13 Nov 2022 05:30:57 +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 1ou5a4-0007Xc-JE for pgsql-general@lists.postgresql.org; Sun, 13 Nov 2022 05:30:56 +0000 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ou5a2-0004WM-HE for pgsql-general@lists.postgresql.org; Sun, 13 Nov 2022 05:30:56 +0000 Received: by mail-oi1-x231.google.com with SMTP id c129so8632841oia.0 for ; Sat, 12 Nov 2022 21:30:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=cxErbgcfh6Iwvp04HT1eyHWaB29Rg323bj68KLgIMwU=; b=Ph63rRWvxkkB6heemIR3nljZkLCXzeCtxYAvKmmc1agwitcYAFFoTjxznAHzObuIXC PpbbTf3dMMk2/J/OIgUZCvCCv6f3aOXuE/fjTbdJlXol9FKzYI372LeabMJwTkxqW0dK 7M1DczTzprAuy0XCiDp1/D44vfIGECTSvklAJzbUrXX/MpWaFSfb2pOn2jULj4dZvrAs kz9Om4El6myzhWsJyvp604YXd5KV6VISM8pgLw67+5ex8zy7x3/UjwZheLd1bfkZKCcv dugp2JNMngm8uatvLafulZqAzxk5uRVm+T7ZKDDLDKhgZoID94dbcljOQ1v1AtISPMqn C8HA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=cxErbgcfh6Iwvp04HT1eyHWaB29Rg323bj68KLgIMwU=; b=BxKSjvr5x2fwX5KYJE854BW7ZjATRBJVKG0Egv0hhNLIyt/GoyetbzhiW58SF9ehNy 7IJL5D35akWCybti0pyfqTNk634XVuCgbeNiCBST4zuGnRTEOB4QBQW8agz/ddYo9Z25 SnIC/rt5VdY7RDjuVoztTl7IL3LVeQKC+lvavqF1JXNQPuc6rlWjdBPnS6kL09/KtGAr GaNF0+Ot/wwIIMh/4yWSUQFPfH6ZLbIALpE5pDOiqLQYNNd9G0Dk2oTFQMt/3QrdZG8Q FA0CmM3Am77UseDIBB84lseGGxlcuVFm9SA0hnS+Q77TtTc6HBdMnbdaUNOjYHo+E3Xc l/PA== X-Gm-Message-State: ANoB5plppK7+PLhxCi7pdv949lqIUv5iM+V79cVrRnx+UL3m6u8yMms4 QBJZJ4lghmthPCJNJrA1RADGZBiG+kY= X-Google-Smtp-Source: AA0mqf5K0JNxXyGJtETjfG2J/8sHErGUElwQHoaS/aXyLQB3ELN26hcEJl/7qSYrYc76w7w/lJt9Jw== X-Received: by 2002:a05:6808:93:b0:350:6b21:53c7 with SMTP id s19-20020a056808009300b003506b2153c7mr3719596oic.156.1668317452252; Sat, 12 Nov 2022 21:30:52 -0800 (PST) Received: from [192.168.88.10] (ip68-230-234-148.no.no.cox.net. [68.230.234.148]) by smtp.googlemail.com with ESMTPSA id r24-20020a4ad4d8000000b0049ea9654facsm2387400oos.32.2022.11.12.21.30.51 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 12 Nov 2022 21:30:51 -0800 (PST) Content-Type: multipart/alternative; boundary="------------OOImYZMAjzekviG400nBWXce" Message-ID: <5bdec7a2-bfec-b0f3-2e23-09ea7c9303cf@gmail.com> Date: Sat, 12 Nov 2022 23:30:50 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: Upgrading to v12 Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <9aa1a829-3367-74cf-1630-a91a4d67d41d@aklaver.com> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------OOImYZMAjzekviG400nBWXce Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/11/22 23:09, Adrian Klaver wrote: > On 11/11/22 20:59, Brad White wrote: >> On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver > > wrote: > >> Yes. The backup is from production. >> V9.4 is running on 5432 on all servers. >> That particular restore happens to be on the dev server. 5433 is v12. >> > > 1) This does not address from your OP: > > "I only need the primary. > Not the half dozen restored copies." > > And then from follow up post: > > "I deleted all the other DBs and left only the primary. > Still getting the same error message, ending with" > > How where the restored copies made on the original cluster? > > 2) For your explanation above, pg_dump from 9.4(5432) to pg_restore > 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore > of said dump file to version 12. When moving up in version you need to use > the newer version of pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4 > instance and then the version 12 pg_restore to the 12 instance. Both > programs are backwards compatible, not forwards compatible. Unless there's some bug (you're running a /really/ old version of 9.4), you might be able to get away with using the 9.4 binary. (I successfully migrated 8.4.17 to 9.6.6 and  9.2.7 databases to 9.6.24, and 9.6.24 databases to 13.8 using the old pg_dump binaries when it was impractical to install the newer Postgresql in parallel with the old binaries.) -- Angular momentum makes the world go 'round. --------------OOImYZMAjzekviG400nBWXce Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 11/11/22 23:09, Adrian Klaver wrote:
On 11/11/22 20:59, Brad White wrote:
On Fri, Nov 11, 2022, 9:57 PM Adrian Klaver <adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>> wrote:

Yes. The backup is from production.
V9.4 is running on 5432 on all servers.
That particular restore happens to be on the dev server. 5433 is v12.


1) This does not address from your OP:

"I only need the primary.
Not the half dozen restored copies."

And then from follow up post:

"I deleted all the other DBs and left only the primary.
Still getting the same error message, ending with"

How where the restored copies made on the original cluster?

2) For your explanation above, pg_dump from 9.4(5432) to pg_restore 12(5433) the issue would be ...\9.4\bin\pg_dump.exe of 9.4 and pg_restore of said dump file to version 12. When moving up in version you need to use the newer version of pg_dump(...\12\bin\pg_dump.exe) to dump the 9.4 instance and then the version 12 pg_restore to the 12 instance. Both programs are backwards compatible, not forwards compatible.

Unless there's some bug (you're running a really old version of 9.4), you might be able to get away with using the 9.4 binary.  (I successfully migrated 8.4.17 to 9.6.6 and  9.2.7 databases to 9.6.24, and 9.6.24 databases to 13.8 using the old pg_dump binaries when it was impractical to install the newer Postgresql in parallel with the old binaries.)

--
Angular momentum makes the world go 'round.
--------------OOImYZMAjzekviG400nBWXce--