MIME-Version: 1.0
References: <CAEHBEOBuoMFWuhHM3L_Zr6o1enELju-Vns6Pknt4TT+6MFQOwQ@mail.gmail.com>
 <fd47b28c-8f6b-4bfb-a393-160c5c3de8c0@aklaver.com> <CAEHBEOD969YrbPH_z9OEmThWx3-w4sMMaHLhZLOQwqCwE8Y58Q@mail.gmail.com>
 <caf4e99941b3c83bb9eab91e33b144b826b68f79.camel@cybertec.at>
 <CAEHBEOBXzkGTqxQSYqmEFN5hbc=zsGWFpU9h8zf7AAPv4VdOWQ@mail.gmail.com>
 <c9699a6fd331d33864fc269060d8d961f784d827.camel@cybertec.at>
 <CAEHBEOBNoG8RkKuCcQQWkbYppMLMzA0MXq+s0kZ6wKWgD7+45Q@mail.gmail.com>
 <099b49ebae94e23f19afdad3f8c9c6e702a3a2d5.camel@cybertec.at>
 <CAEHBEODw8svX557pjB_EL-Os7KWtwi-9Uq=RuCkRKgHVZWw8Bw@mail.gmail.com>
 <6d7e1022-6404-4dab-8467-8d1f6e8b63cb@aklaver.com> <CAEHBEOCpxASoNn=u21kaqOn1A-4YPy_mVfgkEjT3wRT5G4ycbg@mail.gmail.com>
 <CAKAnmmKiPkxVVTQ6-_MieuroWEnemJQEPLKsLjkdbbub--q2ng@mail.gmail.com> <CA+FnnTxg+b2aiYQ92f5CFfhV9kg7YF3s26_dGJG-02ywAtz6sQ@mail.gmail.com>
In-Reply-To: <CA+FnnTxg+b2aiYQ92f5CFfhV9kg7YF3s26_dGJG-02ywAtz6sQ@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Thu, 6 Mar 2025 13:16:56 -0500
Message-ID: <CANzqJaAmNL0_ky6EtXDJ4mXAiW=v1dYM==KkABoCLO=_7oXA2g@mail.gmail.com>
Subject: Re: Quesion about querying distributed databases
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000007d1f11062fb083b7"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaAmNL0_ky6EtXDJ4mXAiW%3Dv1dYM%3D%3DKkABoCLO%3D_7oXA2g%40mail.gmail.com>
Precedence: bulk

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

On Thu, Mar 6, 2025 at 10:47=E2=80=AFAM Igor Korot <ikorot01@gmail.com> wro=
te:

> Hi,
>
> On Thu, Mar 6, 2025, 7:32=E2=80=AFAM Greg Sabino Mullane <htamfids@gmail.=
com>
> wrote:
>
>> On Wed, Mar 5, 2025 at 9:44=E2=80=AFPM me nefcanto <sn.1361@gmail.com> w=
rote:
>>
>>> Anyway, that's why I asked you guys. However, encouraging me to go back
>>> to monolith without giving solutions on how to scale, is not helping.
>>>
>>
>> We did. In addition to the ongoing FDW discussion, I mentioned read-only
>> replicas and Citus. As far as *how* to scale vertically, we can offer
>> general advice (more hardware resources, ramdisks for temp stuff, OS-lev=
el
>> tuning, separate disk mounts). But a lot of it is tuning Postgres for yo=
ur
>> specific situation and your specific bottlenecks. Which we are happy to
>> help with. Once we convince you to not throw the baby out with the
>> bathwater. :)
>>
>> 8 Terabytes of data. A single backup took us more than 21 days
>>
>>
>> Something was fundamentally wrong there.
>>
>
> It could happen on an old and drained hardware... =F0=9F=98=80
>

8TB databases existed 20+ years ago.  Like always, the hardware must fit
the application.

21 days to backup a database absolutely means *many* things were improperly
sized and configured.

--=20
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

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

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Mar 6, 2025 at 10:47=E2=80=AFAM I=
gor Korot &lt;<a href=3D"mailto:ikorot01@gmail.com">ikorot01@gmail.com</a>&=
gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto"><div>Hi,<br><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Mar=
 6, 2025, 7:32=E2=80=AFAM Greg Sabino Mullane &lt;<a href=3D"mailto:htamfid=
s@gmail.com" target=3D"_blank">htamfids@gmail.com</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=
=3D"ltr">On Wed, Mar 5, 2025 at 9:44=E2=80=AFPM me nefcanto &lt;<a href=3D"=
mailto:sn.1361@gmail.com" rel=3D"noreferrer" target=3D"_blank">sn.1361@gmai=
l.com</a>&gt; wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-family:taho=
ma,sans-serif">Anyway, that&#39;s why I asked you guys. However, encouragin=
g me to go back to monolith without giving solutions on how to scale, is no=
t helping.</div></div></blockquote><div><br></div><div>We did. In addition =
to the ongoing FDW discussion, I mentioned read-only replicas and Citus. As=
 far as *how* to scale vertically, we can offer general advice (more hardwa=
re resources, ramdisks for temp stuff, OS-level tuning, separate disk mount=
s). But a=C2=A0lot of it is tuning Postgres for your specific situation and=
 your specific bottlenecks. Which we are happy to help with. Once we convin=
ce you to not throw the baby out with the bathwater. :)</div><div><br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><span style=3D"font-fami=
ly:tahoma,sans-serif">8 Terabytes=C2=A0of data. A single backup took us mor=
e than 21 days</span></blockquote><div><br></div><div>Something was fundame=
ntally wrong there.=C2=A0</div></div></div></blockquote></div></div><div di=
r=3D"auto"><br></div><div dir=3D"auto">It could happen on an old and draine=
d hardware... =F0=9F=98=80</div></div></blockquote><div><br></div><div>8TB =
databases existed 20+ years ago.=C2=A0 Like always, the hardware must fit t=
he application.</div><div><br></div><div>21 days to backup a database absol=
utely means <i>many</i> things were improperly sized and configured.</div><=
div><br></div></div><span class=3D"gmail_signature_prefix">-- </span><br><d=
iv dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">Death to &lt;Reda=
cted&gt;, and butter sauce.<div>Don&#39;t boil me, I&#39;m still alive.<br>=
<div><div>&lt;Redacted&gt; lobster!</div></div></div></div></div></div>

--0000000000007d1f11062fb083b7--