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 1uY7Ua-001OP5-5Q for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 18:20:04 +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 1uY7UW-008t82-Kl for pgsql-general@arkaria.postgresql.org; Sat, 05 Jul 2025 18:20:01 +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 1uY7UW-008t7u-7u for pgsql-general@lists.postgresql.org; Sat, 05 Jul 2025 18:20:00 +0000 Received: from mail-oi1-x22c.google.com ([2607:f8b0:4864:20::22c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uY7UU-005vqx-27 for pgsql-general@lists.postgresql.org; Sat, 05 Jul 2025 18:20:00 +0000 Received: by mail-oi1-x22c.google.com with SMTP id 5614622812f47-40a7322f081so483161b6e.3 for ; Sat, 05 Jul 2025 11:19:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1751739596; x=1752344396; darn=lists.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=ruaaaBVem0g1xME6voUMlNhVbJQfw61QarchK/W9Vn4=; b=Yn+lZDO0i0rOPlOvvv6lQPDHBcfzdr7G9YtgmuNuCduLELEDzmlvheIgtNQ76TMEFw 5cO319J51BoRoittngf4+7BdpInPinXEXDUTkwxzLHOXlFhRJbsm1gLND1MLkZowmLIC GKm754VN0fcmczYSFku3FRCmNG1x8eRv9QqRSCjkXKHquRXrLyc6ivPFKGAxIiQb+C3F P7tKdMAWKWBQ2bv5XnioNH+vTE91+6dOa/no0eFlNgktowRgbir/QgqS5mUyhCFuhosR rEQkEH886z5KggOU8RbnWhjxKAE55ziPqqQU6VJMzD4pS5WAN0G3KgxFHLlWOG1Qp1MR 7HWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1751739596; x=1752344396; 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=ruaaaBVem0g1xME6voUMlNhVbJQfw61QarchK/W9Vn4=; b=KwNjI9MjNcxgJKjnL7uhF0WIszRuRz3c3v9CNQHJd8iML6w4Hkmi82qCw0kEsakp5A lmVwQCV9P4yQ/XSqJJjEG2KIRWS6NLoRXnNx2SaSwEFn26lQ/yqgEQ83ubRN4uz3Nj4C J7jy+BGHVCLsd0Ojlw7Lfj1rJPNbevrCZVpdl8OmX7JSxx+uoG/VL7yn02P4TLbXXyOO 8EAPpAL8GJOhSYMhuWjY+6KO3DtSj7JWdYiKYSkg5B43lqzCuSUysR+DwXWmi0UoiqA/ +f2LkH87mv5UqXL66MXLOVHOdHM0fJPrE80akZMmSMh7M8kMaLwjmYq1ZWUFBl9t4+qT p9Bw== X-Gm-Message-State: AOJu0Yy1tI7R8z3IsOiFllAHE2ULGRBg6FuF+8HIozoW3H4OnSF3MPsH /xNpWsgnY0CZyTkINWMsoU+kXnIvwAfBwpJo36aYGbOamAeiioJzP7RXYkbZ7J3UlsR7ZewOooV ol6u0DVcxOjAsmBYKExbXqKDjEiuWL36BwAWn X-Gm-Gg: ASbGncvI64pz5GeGAf9yUdIocXbB2VNolUwDyYQA+GpIyCL7UmlX2mFTCtsfsd/aU5d JhNmAoyvQ4MuxgMyB2zHGAy8IKPmwJ1cQGvzkcV9TxLoJnqEZNc34YoLjTHLcRUAbLsm/GH1tPm 2rxRu7ZFwbzc+WNfs0sLhyzIG+s7nSjjSf+PYGdhtkaGe+hpFe7N0zZBw+PgPxejdRHrTITPk8L xpaSw== X-Google-Smtp-Source: AGHT+IFX66auIPNKvAC4S7RwTTjinS/Wc0+vqCr5A4mRb+Cink2Tmekm02nwmqkqTYVGhIORDjQBX1MAlqMY8+wASvg= X-Received: by 2002:a05:6808:5245:b0:40b:9307:d71a with SMTP id 5614622812f47-40d0439e3cdmr4602730b6e.14.1751739596018; Sat, 05 Jul 2025 11:19:56 -0700 (PDT) MIME-Version: 1.0 References: <20250705125207.31b4d475@pfortin.com> In-Reply-To: From: Ron Johnson Date: Sat, 5 Jul 2025 14:19:45 -0400 X-Gm-Features: Ac12FXy0YFKtXcu9p2R1a63w_F4I9UOCzvfKtfndUakcpzyAZXaWe9sl6lCJz-I Message-ID: Subject: Re: pg_upgrade: can I use same binary for old & new? To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000005c1901063932a8d6" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000005c1901063932a8d6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Jul 5, 2025 at 2:11=E2=80=AFPM Adrian Klaver wrote: > On 7/5/25 09:52, Pierre Fortin wrote: > > Hi, > > > > [Hope this gets through after dumping DKIM-ignorant mail provider.] > > > > Wanting to upgrade from: > > PostgreSQL 15.13 on x86_64-mageia-linux-gnu, > > compiled by gcc (Mageia 15.1.0-1.mga10) 15.1.0, 64-bit > > to: > > PG 17.5 > > > > Way back, I was able to use -k|--link option on pg_upgrade (PG13 to > PG15); > > but since then: > > > > - my DB has grown to over 8TB > > How did you measure above? > > > - even with ~70TB, I don't have enough contiguous disk space to > > dump/restore > > What was the pg_dump command? For something that big, he must have been doing an uncompressed plain format dump instead of a directory/custom format dump. Maybe even added --attribute-inserts too. --=20 Death to , and butter sauce. Don't boil me, I'm still alive. lobster! --0000000000005c1901063932a8d6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Jul 5, 2025 at 2:11=E2=80=AFPM Ad= rian Klaver <adrian.klaver@= aklaver.com> wrote:
On 7/5/25 09:52, Pi= erre Fortin wrote:
> Hi,
>
> [Hope this gets through after dumping DKIM-ignorant mail provider.] >
> Wanting to upgrade from:
> PostgreSQL 15.13 on x86_64-mageia-linux-gnu,
> compiled by gcc (Mageia 15.1.0-1.mga10) 15.1.0, 64-bit
> to:
> PG 17.5
>
> Way back, I was able to use -k|--link option on pg_upgrade (PG13 to PG= 15);
> but since then:
>
> - my DB has grown to over 8TB

How did you measure above?

> - even with ~70TB, I don't have enough contiguous disk space to >=C2=A0 =C2=A0 dump/restore

What was the pg_dump command?

For something= that big, he must have been doing an uncompressed plain format dump instea= d of a directory/custom format dump.=C2=A0 Maybe even added --attribute-inserts=C2=A0too.
--
Death to <Redacted&g= t;, and butter sauce.
Don't boil me, I'm still alive.
<= div><Redacted> lobster!
--0000000000005c1901063932a8d6--