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 1sdwKR-002R9K-Ir for pgsql-general@arkaria.postgresql.org; Tue, 13 Aug 2024 18:33:07 +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 1sdwKQ-005kIn-7j for pgsql-general@arkaria.postgresql.org; Tue, 13 Aug 2024 18:33:06 +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 1sdwKP-005kIF-St for pgsql-general@lists.postgresql.org; Tue, 13 Aug 2024 18:33:05 +0000 Received: from mail-oi1-x234.google.com ([2607:f8b0:4864:20::234]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdwKN-004h6Z-Np for pgsql-general@postgresql.org; Tue, 13 Aug 2024 18:33:05 +0000 Received: by mail-oi1-x234.google.com with SMTP id 5614622812f47-3db1657c0fdso3921710b6e.1 for ; Tue, 13 Aug 2024 11:33:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723573981; x=1724178781; 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=Hrd272SznKDB+QRP9vWnwXNGBjwbI1rn1k/8fSmtjqk=; b=mm+zEDPCEYm9fF5kWq3w5r2g3hTZe2jO1Nw+0cLvWAqUJX8pdeS86yU7P0qtgmuoL+ pzybCl30U6DMJBQx7dDaaepCwHLz/HLwPuxFBwS0Abqn4dEXgbvA/P1XB7HMy9wRMcUc huHhzKjOQruQyQAim8Pt+2Rry2h+M5mP2NFmtdtISIrQ3GdIoSjBXdmGe57N22kVDiF0 YrL/TNW5SxsfN3v3KbELZwRNeJ0Z3e2MzGZgJmWNPHrvZfBj/URSL04h4b7g5nUkpt0R t8Cd2/ouf/dgZ0BxfhyAWqsjxJ/G4a0ZreysI5EXN7JhUrnWDGL1IrAt5AQXDroj41dU Xf8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723573981; x=1724178781; 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=Hrd272SznKDB+QRP9vWnwXNGBjwbI1rn1k/8fSmtjqk=; b=sTZVPiUBBXbs2y/ivArXC+JqIAyFBYUb/PtTz+drAJIaWIks00oj3sOUqo5/0dSxcN j8yxNcEkVkpLe+LjCdKUCSFzxPGY3FDSSSaQM54bSLdVkoe4KacY834IT/BUTjvvn7MP KMV3l9qxoN3wbBtm9ShHlvJ6UEGHWGhAej9L7OfU1bl17+1nCMGZ9SemtGGBkZlUGL3C /H2q1nIPjAwz5ViQg+EGSVBdWJUeNXZOaH3w0p9hAKaDjNt2e3G3QkwTT6fgnYJgvWZO sgYkhIkrgk/DE2h/DGRA4tWzp9mG/vwkP0ICfwT7ik6wn1YpG4rkuOgDtZZWtozVEEbe Zb1g== X-Gm-Message-State: AOJu0YxvcpYsuDpx9zbFeduNvlTs/7FXgNegDRgEx6blZvS1TOmbLAgX iSSyECJJMWmkIprNe29a0OKDj2urDZdT0x9PIATcAy3pZl4Z4u80Rk8aJKYXuSjETBH4KA51w6d zYIx+jPxTuE5zZfsXm9rUHF8Q3YuG9w== X-Google-Smtp-Source: AGHT+IG/cMpZxW9bmhEjFlT8AWCkYlKwDARR1pzKN8ytkn5WjRieCsC++O6uuqhFbx1nVGIIHM+gWr0Zs9AUt5zB7MI= X-Received: by 2002:a05:6808:21a6:b0:3d9:e1d1:1580 with SMTP id 5614622812f47-3dd299154f4mr352140b6e.21.1723573981434; Tue, 13 Aug 2024 11:33:01 -0700 (PDT) MIME-Version: 1.0 References: <37ed3aef-58e6-417b-8015-cdf030a6df4b@vondra.me> In-Reply-To: <37ed3aef-58e6-417b-8015-cdf030a6df4b@vondra.me> From: Ron Johnson Date: Tue, 13 Aug 2024 14:32:50 -0400 Message-ID: Subject: Re: PG Dump on 11 - Restore on 16 - is possible? To: Postgres General Content-Type: multipart/alternative; boundary="000000000000e85c42061f94d698" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e85c42061f94d698 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Aug 13, 2024 at 2:21=E2=80=AFPM Tomas Vondra wrot= e: > On 8/13/24 11:47, Durumdara wrote: > > Hello! > > > > We have to upgrade our server. The PG upgrade is impossible because of > > too much data. > > I'm not sure I understand. What exactly is the problem with the amount > of data? > OP has a physical server, and the cabinet's disk trays are all full (or at least not enough free trays to add enough disk space). But, you say, 20TB disks exist!! Yeah, and the channel speed is slow. Besides, given that it's PG 11, the OS (RHEL?) is probably also EOL (or soon to be). Thus, better to buy a new / faster server, install RHEL9 and PG 16. --=20 Death to America, and butter sauce. Iraq lobster! --000000000000e85c42061f94d698 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, Aug 13, 2024 at 2:21=E2=80=AFPM T= omas Vondra <tomas@vondra.me> = wrote:
On 8/13/24 11:47, Durumdara wrote:
> Hello!
>
> We have to upgrade our server. The PG upgrade is impossible because of=
> too much=C2=A0data.

I'm not sure I understand. What exactly is the problem with the amount<= br> of data?=C2=A0

OP has a physical server, and the cabinet= 's disk trays are all full (or at least not enough free trays to add en= ough disk space).

But, you say, 20TB d= isks exist!!=C2=A0 Yeah, and the channel speed is slow.=C2=A0 Besides, give= n that it's PG 11, the OS (RHEL?) is probably also EOL (or soon to be).=

Thus, better to buy a new / faster server, instal= l RHEL9 and PG 16.

--
Death to America, and butter sauce.
Iraq lobster!
--000000000000e85c42061f94d698--