Re: Quesion about querying distributed databases

From: Igor Korot <ikorot01(at)gmail(dot)com>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: me nefcanto <sn(dot)1361(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Quesion about querying distributed databases
Date: 2025-03-06 15:47:21
Message-ID: CA+FnnTxg+b2aiYQ92f5CFfhV9kg7YF3s26_dGJG-02ywAtz6sQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On Thu, Mar 6, 2025, 7:32 AM Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:

> On Wed, Mar 5, 2025 at 9:44 PM me nefcanto <sn(dot)1361(at)gmail(dot)com> wrote:
>
>> 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-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.
>

It could happen on an old and drained hardware... 😀

Thank you.

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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Igor Korot 2025-03-06 16:34:02 Re: Error on query execution
Previous Message Greg Sabino Mullane 2025-03-06 13:31:54 Re: Quesion about querying distributed databases