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 1sd11k-00COEw-5f for pgsql-admin@arkaria.postgresql.org; Sun, 11 Aug 2024 05:22:00 +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 1sd11g-00B9KC-IO for pgsql-admin@arkaria.postgresql.org; Sun, 11 Aug 2024 05:21:56 +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 1sd11g-00B9K2-00 for pgsql-admin@lists.postgresql.org; Sun, 11 Aug 2024 05:21:56 +0000 Received: from mail-ed1-x531.google.com ([2a00:1450:4864:20::531]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sd11Z-00497P-7f for pgsql-admin@postgresql.org; Sun, 11 Aug 2024 05:21:54 +0000 Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-5b8c2a61386so4023760a12.2 for ; Sat, 10 Aug 2024 22:21:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723353707; x=1723958507; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XtfseyuOpdpQ1s9ro7d9eqnw+OCSm9AnBm3Dc5x/vb8=; b=c+isAOKAIYasjnfIVjVhHyRDb1hCzSI5vfb2nTOlJ4+vrNQruNbcCVjFy73TPTHs6n 4f/Q5aY2w4Jy9dlcJOcYWM4g9CXq1cT3hKGEU5cv7594Gx/a57l8vnl37iUgF1K9lS2a jHQGMZMpEKojnu/jqMAvK9nMSUvUFJnz7R/+VI0qYsGibTuVd/OY39eNj+PRINJ+lMhZ 2al8finI5jPiGtdu92lHBVn5F1NgRFVaEcHmVfUxzS3A4POowX19n6whkd8Ba1gkHOna QCcdznhz+k/aZeTs9/Jb/NtINf0ycN+W+VYH0qPCLKm6ykdxP0qEF3w66AImBarPs9tl mmXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723353707; x=1723958507; h=cc: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=XtfseyuOpdpQ1s9ro7d9eqnw+OCSm9AnBm3Dc5x/vb8=; b=V1CVL48AiaG4GrLgnMggNi3lYyNK6B6gAFTadqPCPdkGjvkEeGCGsFOUYEpbxwG5oW FPmR7vx7gSZAYbQ6cP7fDuXgjaLJx1yuFXNFSHfTdf7AYczHnhcswZBAhLBZzGzF1vkt wEDEwbtiVnKejo2LsmEEQ3FalifZcVK/wuFUSQ1RqWEaG9e50/vGeEIFEPJ7xxK7YOfO isKktRh54Rhp2KZXkD5N0WVecynsWu3I7cdmZeDxOBc2/zdknZHz3iC5wTg3/LQRI+Sq tECrJOCSBAIbLrprCuAf1ofNhwiEEYEyOzdEZQ8hC/fi8Fc7/ZbBP6qc93vVLI14nAP4 nl0w== X-Gm-Message-State: AOJu0YyYcB+a3MLavppEewql5OCN3Jdx2rwhhB5kBF4In2AYMROzWt5v GwgOcXgRJUzOBv9TmmCdgmHneCUSUREkHlnFlA8eDWXtMOCIbLIm6NOBXfimmbl0hr02GTMJnzd QHXOheVMGf1HUxnMun0/x4MQ/2HM= X-Google-Smtp-Source: AGHT+IGSjzlXVF4ZU0/3V9Tgos9tHhzcrBMSlbXEg0x47cTJG0d9wYpYYb1eULV9zKrS7j5dW9FPSlYwrv38K4/UbPU= X-Received: by 2002:a17:907:9807:b0:a77:cd51:3b32 with SMTP id a640c23a62f3a-a80aa67e1f1mr342573566b.62.1723353706671; Sat, 10 Aug 2024 22:21:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Wasim Devale Date: Sun, 11 Aug 2024 10:51:34 +0530 Message-ID: Subject: Re: Migration from CentOS7 to RedHat 9 To: Ron Johnson Cc: pgsql-admin Content-Type: multipart/alternative; boundary="00000000000082362a061f618d55" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000082362a061f618d55 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks it took 3 hours to complete the restoration. The existing CentOS7 resources were limited as you rightly said about CPU and all. Thanks On Sun, 11 Aug, 2024, 12:06=E2=80=AFam Ron Johnson, wrote: > "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 = wrote: > >> Yes, I used the same command I changed the values for this email. And >> that 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! >>> >> > > -- > Death to America, and butter sauce. > Iraq lobster! > --00000000000082362a061f618d55 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Thanks it took 3 hours to complete the restoration. The exis= ting CentOS7 resources were limited as you rightly said about CPU and all. = Thanks


On Sun= , 11 Aug, 2024, 12:06=E2=80=AFam Ron Johnson, <ronljohnsonjr@gmail.com> wrote:
"RHEL9" has almost no= thing to do with how fast it will restore.=C2=A0 It's all about how fas= t 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 <wasimd60@gmail.= com> wrote:

Yes, I used the same command I= changed the values for this email. And that particular table with BLOBS to= ok 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.c= om> wrote:
On Sat, Aug 10, 2024 at 7:14=E2=80=AFAM= Wasim Devale <wasimd60@gmail.com> wrote:
<= div dir=3D"auto">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.=C2=A0 Is this a copy/paste of what you ran?

=
<= div dir=3D"auto">Is this normal?

Maybe.=C2=A0 Blobs are slow.=C2=A0 I'd have done a multi-threaded= pg_dump, though blobs might be the bottleneck.

<= span class=3D"gmail_signature_prefix">--
Death to America, and butter sauce.Iraq lobster!


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