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>
In-Reply-To: <CAEHBEOCpxASoNn=u21kaqOn1A-4YPy_mVfgkEjT3wRT5G4ycbg@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Thu, 6 Mar 2025 08:31:54 -0500
Message-ID: <CAKAnmmKiPkxVVTQ6-_MieuroWEnemJQEPLKsLjkdbbub--q2ng@mail.gmail.com>
Subject: Re: Quesion about querying distributed databases
To: me nefcanto <sn.1361@gmail.com>
Cc: Adrian Klaver <adrian.klaver@aklaver.com>, Laurenz Albe <laurenz.albe@cybertec.at>, 
	pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000a55bfe062fac8980"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmKiPkxVVTQ6-_MieuroWEnemJQEPLKsLjkdbbub--q2ng%40mail.gmail.com>
Precedence: bulk

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

On Wed, Mar 5, 2025 at 9:44=E2=80=AFPM me nefcanto <sn.1361@gmail.com> wrot=
e:

> Anyway, that's why I asked you guys. However, encouraging me to go back t=
o
> 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-level
tuning, separate disk mounts). But a lot of it is tuning Postgres for your
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.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

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

<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">sn.1361@gmail.com</a>&gt=
; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-f=
amily:tahoma,sans-serif">Anyway, that&#39;s why I asked you guys. However, =
encouraging me to go back to monolith without giving solutions on how to sc=
ale, is not 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 (m=
ore hardware resources, ramdisks for temp stuff, OS-level tuning, separate =
disk mounts). But a=C2=A0lot of it is tuning Postgres for your specific sit=
uation and your specific bottlenecks. Which we are happy to help with. Once=
 we convince 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-family:tahoma,sans-serif">8 Terabytes=C2=A0of data. A single backup t=
ook us more than 21 days</span></blockquote><div><br></div><div>Something w=
as fundamentally wrong there.=C2=A0</div><div><br></div></div><div dir=3D"l=
tr" class=3D"gmail_signature"><div dir=3D"ltr"><div>Cheers,</div><div>Greg<=
/div><div><br></div><div>--</div><div>Crunchy Data - <a href=3D"https://www=
.crunchydata.com" target=3D"_blank">https://www.crunchydata.com</a></div><d=
iv>Enterprise Postgres Software Products &amp; Tech Support</div><div><br><=
/div></div></div></div>

--000000000000a55bfe062fac8980--