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 1sdqCn-001TLc-AB for pgsql-general@arkaria.postgresql.org; Tue, 13 Aug 2024 12:00:49 +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 1sdqCl-003Nbj-BH for pgsql-general@arkaria.postgresql.org; Tue, 13 Aug 2024 12:00:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sdqCk-003Nba-WB for pgsql-general@lists.postgresql.org; Tue, 13 Aug 2024 12:00:47 +0000 Received: from mail-oo1-xc2e.google.com ([2607:f8b0:4864:20::c2e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdqCb-004e5y-7s for pgsql-general@postgresql.org; Tue, 13 Aug 2024 12:00:46 +0000 Received: by mail-oo1-xc2e.google.com with SMTP id 006d021491bc7-5d5ed6f51cfso3632316eaf.0 for ; Tue, 13 Aug 2024 05:00:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723550435; x=1724155235; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=Ayrv8k25TVko3tWBBG6x7om8qlISCk3hXKCFBcdCRKw=; b=OyM9inaav43ODxGe9+76UEUG73H4p7JrOkyw9efE0zMzB0sH97O6HC73WNFMm5vr0P s6sky9plvfdc0ymPJ917rUF0pgNnOQS7L8pi+K6Pwdo3E0xUbdrUTiaStQSP6DFGeqfM 6i6JKjCioGr7hWyLR2TrPflzLaDDHUx9/HXduFNIN4JG9hYVuzsoBYMeh0Yr4lxs4lT7 HUgsZWXtXDxrEBLZkl7xfypj0hRdsb8DKvcyYF4+75e/ZGfMzUXHUQFN/aeJHkNP8t1k 3ZNrmWma4BQdBNg/1dtRsk0fGFxkERp+Om6tTW2n7qUYE7mnQNnArcxrszyP2w9cJZ4Z ntUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723550435; x=1724155235; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Ayrv8k25TVko3tWBBG6x7om8qlISCk3hXKCFBcdCRKw=; b=HqZR2m8JjVN4t6IzfR4E8QJWSsX/DRcrDTITiuUZJfd0A4UrBj5Ex8k1l4p3G8SH3Z PE54JfZkFk/vEo+EdGNqSGi9dWaY/HQflTW1LVDKqhJvkkkaEMEl5qxyqDKE0thtqEQD m7mfzgg8isK2pvVcBFIJiJo4K/8bVkxUG+0HzgQV91/ojKyUjdB2iI//ZKMo5aeuUS91 QA1kcqbaL862bqS+JKCBkzNSJzPKSQlx3AF4UoABPfbGIXfrU1eDpMwHNuAuKMd/YU4D 6uIUEyWeaRn6ZfXyS1HtM6Q33qtcpquzrklMtRttk8cxK2sckoOHtm19VvVAshAk0XOD vP5Q== X-Gm-Message-State: AOJu0YzYwnosfIPH63ZrDcDTSYt1dAxpZZ6F47BM8VyOxDF+3nzLSfNM U6KAU/huwfxD3yXAZ+BYihRqaZJDGUyzXbwPwUyPQtSZ0luHOspBt26ObSyvR8fOAnGNbTWtYxu gkFebJTinkDw5dRUhGmDwTBpRq4OS+Xe7 X-Google-Smtp-Source: AGHT+IEh1G3vUCi3q6vi8r/UDj/6y6nVZyXHkLk7iWQlzGlgRY6xS7VZ5FKesYI3dsaZatnaDha1JSq9J/hwN8TsYSw= X-Received: by 2002:a05:6820:221e:b0:5d6:79a:c4d6 with SMTP id 006d021491bc7-5da68802904mr3727444eaf.3.1723550434371; Tue, 13 Aug 2024 05:00:34 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Tue, 13 Aug 2024 08:00:23 -0400 Message-ID: Subject: Re: PG Dump on 11 - Restore on 16 - is possible? To: pgsql-general Content-Type: multipart/alternative; boundary="00000000000064b97b061f8f5b2e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000064b97b061f8f5b2e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 13, 2024 at 5:47=E2=80=AFAM Durumdara wro= te: > Hello! > > We have to upgrade our server. The PG upgrade is impossible because of to= o > much data. > So we will create a new server with PG 16, and we have to migrate the > databases one by one (from a PG 11 server). > I'd also recommend that you update the PG 11 server to 11.22 if possible. It can hopefully be found here: https://yum.postgresql.org/repopackages/#pgredhatoldrepos --=20 Death to America, and butter sauce. Iraq lobster! --00000000000064b97b061f8f5b2e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Aug 13, 2024 at 5:47=E2=80=AFAM D= urumdara <durumdara@gmail.com= > wrote:
Hello!

We have t= o upgrade our server. The PG upgrade is impossible because of too much=C2= =A0data.
So we will create a new server with PG 16, and we have t= o migrate the databases one by one (from a PG 11 server).

I'd also recommend that you update the PG 11= server to 11.22 if possible.

<= div>
--
Death to America,= and butter sauce.
Iraq lobster!
--00000000000064b97b061f8f5b2e--