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 1scqxH-00Aui7-Bx for pgsql-admin@arkaria.postgresql.org; Sat, 10 Aug 2024 18:36:43 +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 1scqxF-00A68n-1V for pgsql-admin@arkaria.postgresql.org; Sat, 10 Aug 2024 18:36:41 +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 1scqxE-00A68f-M0 for pgsql-admin@lists.postgresql.org; Sat, 10 Aug 2024 18:36:40 +0000 Received: from mail-oo1-xc2f.google.com ([2607:f8b0:4864:20::c2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1scqxC-0044mH-2q for pgsql-admin@postgresql.org; Sat, 10 Aug 2024 18:36:39 +0000 Received: by mail-oo1-xc2f.google.com with SMTP id 006d021491bc7-5d5f24d9df8so1559957eaf.2 for ; Sat, 10 Aug 2024 11:36:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723314996; x=1723919796; 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=PiZ3nrO/yOlOdT/tfcR6KKcnI8/MBBUhcPDfYzSWiVQ=; b=RgY3/8iMqw6KEyI9KpfmDyJHBkUD8Kl8zOxCb+mzjhyJWmjwlzw1z2y9ZzGPhSLs5g 6TqyQbnRU6CgmeNjMcG/5A9BISn7Qzhw2qFIs29Q9az4+ThUio9JeVKHS6IhXWwaHLHU t99JI5L8gu/NE5AyJOyUBb1CrFVUM36Mj/WVD0aKkMnGAl3/lNtnxgbREhzvKrLYS3Gy oaJJWAsIfvg5B+FJDcekZX0j8JujSPfel5aklsgXqZKncQD4XN9P6+OuqHDmqnyBZyuS aUpldG/RcXsYSQkeNsM3WrssdQXgP3kMSsFxnvO5TaBZ7xqvxhQKeWuvyNLyS5y4NpuE ByWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723314996; x=1723919796; 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=PiZ3nrO/yOlOdT/tfcR6KKcnI8/MBBUhcPDfYzSWiVQ=; b=nNent4Um72c/XRJi16oOpA43cOiaX8Hd4PHk1KKocWsKynUhMGS9WlVaPNS1sLHysq 5Tldp4PlyOZDNlWEEwB9Dc9EvtUvGGD53xthvMag0N20LfMrw5+LYeXKUrx36GU8TaNO iE7aa128fTgOQQAslTvbw7AvOJ10D4mJJc4ZftHg7nG/l2vgQWQ+jBhfiGPC+JT6gnqi qgJ09L4gUzmcQPVxQlRMl7vHcqXYhSJ19p/dabQTjDs40oSQdHpGoEe07hwPTVfCClMy GCYPKHHb71eDuDbusfl/yEn5qg8K33XGbNjYzAYHH166nClvYjHk2ayQZani/KRIV2gH +mAA== X-Gm-Message-State: AOJu0Yzi79wzeWBsyny2b07X3ba2wPuqH6AXRUpqaSdwfWNmKuih5qUx l4JO6mf0xRPEbOREfV2/wN470EmYSrwDoGy4jDFSeBqnvrTExGzpizPt7vZl0zBB3L9U14IyEmR /Ih5CxyYtws3AMLcfjVumSPIzwJlyaA== X-Google-Smtp-Source: AGHT+IFb6ncBgRfXKpkUSVNjdLdTFLRpENkIZjQg3daf3y/Vx59T5v9EpWtRBZ6kj34Qrxr5oo7GC44SQ3G8CGQlKzY= X-Received: by 2002:a05:6820:1c85:b0:5d8:4845:1a4e with SMTP id 006d021491bc7-5d867aff35emr5783303eaf.0.1723314996523; Sat, 10 Aug 2024 11:36:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ron Johnson Date: Sat, 10 Aug 2024 14:36:25 -0400 Message-ID: Subject: Re: Migration from CentOS7 to RedHat 9 To: pgsql-admin Content-Type: multipart/alternative; boundary="000000000000343d56061f588a41" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000343d56061f588a41 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable "RHEL9" has almost nothing to do with how fast it will restore. It's all about how fast your disk are, number of CPUs, postgresql.conf settings. And, of course, blobs are slow. On Sat, Aug 10, 2024 at 9:26=E2=80=AFAM Wasim Devale w= rote: > Yes, I used the same command I changed the values for this email. And tha= t > particular table with BLOBS took a longer time. > > I am running a pg_restore now using -j 10 in the command. Please confirm, > what you anticipate, will it take same time for restoration on Red Hat 9? > > Thanks, > Wasim > > On Sat, 10 Aug, 2024, 6:35=E2=80=AFpm Ron Johnson, > wrote: > >> On Sat, Aug 10, 2024 at 7:14=E2=80=AFAM Wasim Devale wrote: >> >>> Hi All >>> >>> I took dump via pg_dump doing ssh from Red hat it took almost 10 hours >>> for 400GB data including 99GB of BLOBS large objects. >>> >>> ssh postgres@ipaddre "pg_dump -U postgres -d DB1 F c -b -v" > >>> /path/pg.dump >>> >> >> I see a typo. Is this a copy/paste of what you ran? >> >> Is this normal? >>> >> >> Maybe. Blobs are slow. I'd have done a multi-threaded pg_dump, though >> blobs might be the bottleneck. >> >> -- >> Death to America, and butter sauce. >> Iraq lobster! >> > --=20 Death to America, and butter sauce. Iraq lobster! --000000000000343d56061f588a41 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
"RHEL9" has almost nothing to do with how f= ast it will restore.=C2=A0 It's all about how fast your disk are, numbe= r of CPUs, postgresql.conf settings.

And, of cours= e, blobs are slow.

On Sat, Aug 10, 202= 4 at 9:26=E2=80=AFAM Wasim Devale <wasimd60@gmail.com> wrote:

Yes, I used th= e same command I changed the values for this email. And that particular tab= le with BLOBS took a longer time.

I am running a pg_restore now using -j 10 in the command. Pl= ease confirm, what you anticipate, will it take same time for restoration o= n Red Hat 9?

Thanks,
Wasim


On Sat= , 10 Aug, 2024, 6:35=E2=80=AFpm Ron Johnson, <ronljohnsonjr@gmail.com> wrote:
=
On Sat, Aug 10, 2024 at 7:14=E2=80=AFAM Wasim Devale <<= a href=3D"mailto:wasimd60@gmail.com" rel=3D"noreferrer" target=3D"_blank">w= asimd60@gmail.com> wrote:
Hi All

I took dump via pg_dump doing ssh fr= om Red hat it took almost 10 hours for 400GB data including 99GB of BLOBS l= arge objects.

ssh postgr= es@ipaddre "pg_dump -U postgres -d DB1 F c -b -v" > /path/pg.d= ump

I see a typo.=C2=A0 Is this= a copy/paste of what you ran?

Is this norma= l?

Maybe.=C2=A0 Blobs are s= low.=C2=A0 I'd have done a multi-threaded pg_dump, though blobs might b= e the bottleneck.

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


--
Death to America, and butter sauce.
Iraq lobster!
<= /div>
--000000000000343d56061f588a41--