MIME-Version: 1.0
References: 
 <CAP-pBm9YJqrZQgrH1ZsFt9RbTsOTKH1niS5bEhhB_mSsT49B5Q@mail.gmail.com>
 <e122a2f0a0411056585f4b6beb053756a715705b.camel@cybertec.at>
 <CAP-pBm-Y=b6YxHPag0TLertO=7OCo1kN8RVjBg5mvJNx6Y56KA@mail.gmail.com>
 <4f6b5b081397ba9de49725f87d9ad3e40bf30dbf.camel@cybertec.at>
 <5DA36CEB-A299-41C5-8C00-FC1631E6EE8E@elevated-dev.com>
 <CAP-pBm-_SNXLaOfPbMxs5WWykwfMdJY6Nmgs21oHo4bJFFxXxg@mail.gmail.com>
 <06090D46-9CB3-4491-A395-47654C4A2517@elevated-dev.com>
 <CAP-pBm9VhXwDbrmQwRTLnFHhDq-f88V97ysL3KrxOX4YGJwYcw@mail.gmail.com>
In-Reply-To: 
 <CAP-pBm9VhXwDbrmQwRTLnFHhDq-f88V97ysL3KrxOX4YGJwYcw@mail.gmail.com>
From: kasem adel <kasemadel8@gmail.com>
Date: Sat, 18 Jan 2025 00:13:23 +0200
Message-ID: 
 <CAP-pBm-Uk9VtTppHu=mrRO=DqM-=asdp_VyQRkFHDosY2tS8vA@mail.gmail.com>
Subject: Re: Advice Needed: Simultaneous Upgrade of Two-Node PostgreSQL 11
 Cluster
To: Scott Ribe <scott_ribe@elevated-dev.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000dc242b062bee3840"
Archived-At: 
 <https://www.postgresql.org/message-id/CAP-pBm-Uk9VtTppHu%3DmrRO%3DDqM-%3Dasdp_VyQRkFHDosY2tS8vA%40mail.gmail.com>
Precedence: bulk

--000000000000dc242b062bee3840
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Dears,

I hope this message finds you well.

Thank you for your support. After completing the upgrade process, we
encountered high disk IO due to queries selecting incorrect plans for
specific table. When we ran ANALYZE, it did not choose the correct plan,
likely because we are using the default ANALYZE settings, and our data size
is approximately 1.8 TB. Could you kindly provide a solution to address
this issue?

Thank you in advance for your assistance.


=D9=81=D9=8A =D8=A7=D9=84=D8=AC=D9=85=D8=B9=D8=A9=D8=8C =D9=A1=D9=A7 =D9=8A=
=D9=86=D8=A7=D9=8A=D8=B1 =D9=A2=D9=A0=D9=A2=D9=A5 =D9=A1=D9=A0:=D9=A5=D9=A6=
 =D9=85 kasem adel <kasemadel8@gmail.com> =D9=83=D8=AA=D8=A8:

> Dear Scott Ribe,
>
> Thanks for your support after upgrade process we faced high disk IO
> because query chose wrong  plann but when run analyze not chose the corre=
ct
> plan because we are used default analyze and data size is 1.8 TB can you
> provide us with solution to solve this issue.
>
> Thanks
>
>
>
> =D9=81=D9=8A =D8=A7=D9=84=D8=AE=D9=85=D9=8A=D8=B3=D8=8C =D9=A9 =D9=8A=D9=
=86=D8=A7=D9=8A=D8=B1 =D9=A2=D9=A0=D9=A2=D9=A5 =D9=A3:=D9=A4=D9=A4 =D9=85 S=
cott Ribe <scott_ribe@elevated-dev.com>
> =D9=83=D8=AA=D8=A8:
>
>> > On Jan 7, 2025, at 6:50=E2=80=AFAM, kasem adel <kasemadel8@gmail.com> =
wrote:
>> >
>> > Kindly be informed that database size is 1.8 TB and we have an low
>> network bandwidth between two node 10 mbps and to transfer the data from
>> scratch that will take from 21 day to 30 day  for this we need solution =
in
>> upgrade to prevent load data from scratch .
>>
>> Yes, and I gave you alternatives taking that into account. I think you
>> have all the answers you're going to get, and now have to study them and
>> choose an approach.
>
>

--000000000000dc242b062bee3840
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto" style=3D"font-size:12.8px"><p>Dears,</p=
><p>I hope this message finds you well.</p><p>Thank you for your support. A=
fter completing the upgrade process, we encountered high disk IO due to que=
ries selecting incorrect plans for specific table. When we ran <code>ANALYZ=
E</code>, it did not choose the correct plan, likely because we are using t=
he default <code>ANALYZE</code> settings, and our data size is approximatel=
y 1.8 TB. Could you kindly provide a solution to address this issue?</p><p>=
Thank you in advance for your assistance.</p></div><div dir=3D"auto" style=
=3D"font-size:12.8px"><br></div></div><br><div class=3D"gmail_quote gmail_q=
uote_container"><div dir=3D"ltr" class=3D"gmail_attr">=D9=81=D9=8A =D8=A7=
=D9=84=D8=AC=D9=85=D8=B9=D8=A9=D8=8C =D9=A1=D9=A7 =D9=8A=D9=86=D8=A7=D9=8A=
=D8=B1 =D9=A2=D9=A0=D9=A2=D9=A5 =D9=A1=D9=A0:=D9=A5=D9=A6 =D9=85 kasem adel=
 &lt;<a href=3D"mailto:kasemadel8@gmail.com">kasemadel8@gmail.com</a>&gt; =
=D9=83=D8=AA=D8=A8:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"aut=
o">Dear Scott Ribe,<div dir=3D"auto"><br></div><div dir=3D"auto">Thanks for=
 your support after upgrade process we faced high disk IO because query cho=
se wrong=C2=A0 plann but when run analyze not chose the correct plan becaus=
e we are used default analyze and data size is 1.8 TB can you provide us wi=
th solution to solve this issue.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto">Thanks=C2=A0</div><div dir=3D"auto"><br><div dir=3D"auto"><br></d=
iv></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">=D9=81=D9=8A =D8=A7=D9=84=D8=AE=D9=85=D9=8A=D8=B3=D8=8C =D9=A9 =D9=
=8A=D9=86=D8=A7=D9=8A=D8=B1 =D9=A2=D9=A0=D9=A2=D9=A5 =D9=A3:=D9=A4=D9=A4 =
=D9=85 Scott Ribe &lt;<a href=3D"mailto:scott_ribe@elevated-dev.com" target=
=3D"_blank" rel=3D"noreferrer">scott_ribe@elevated-dev.com</a>&gt; =D9=83=
=D8=AA=D8=A8:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&gt; On Jan 7, 2025, =
at 6:50=E2=80=AFAM, kasem adel &lt;<a href=3D"mailto:kasemadel8@gmail.com" =
rel=3D"noreferrer noreferrer" target=3D"_blank">kasemadel8@gmail.com</a>&gt=
; wrote:<br>
&gt; <br>
&gt; Kindly be informed that database size is 1.8 TB and we have an low net=
work bandwidth between two node 10 mbps and to transfer the data from scrat=
ch that will take from 21 day to 30 day=C2=A0 for this we need solution in =
upgrade to prevent load data from scratch .<br>
<br>
Yes, and I gave you alternatives taking that into account. I think you have=
 all the answers you&#39;re going to get, and now have to study them and ch=
oose an approach.</blockquote></div>
</blockquote></div>

--000000000000dc242b062bee3840--