Re: Challenges with huge postgresql deployments in 300+ TBs

From: kavya chandren <kavyachandren(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Challenges with huge postgresql deployments in 300+ TBs
Date: 2026-10-08 15:56:19
Message-ID: CAPXWBGY8OBgFrTUfMAqWgiYVK-Hc1CvUaREhPGwGYwHvK2sGXg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Adrian,

Intention is to get away from Oracle and get committed to Open source
Postgresql.

On Thu, Oct 8, 2026 at 8:20 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:

> On 10/8/26 12:05 AM, kavya chandren wrote:
> > Hi,
> >
> > We have an oracle deployment running in 300+ TB. Apart from migration
> > challenges, do we foresee any operational challenges? I have not heard
> > of something huge prior. This would be highly helpful in planning
> further.
>
> Why the change?
>
> Is this a pricing issue or are you looking to get something else out of
> the migration?
>
> >
> > Few challenges which caught my attention include,
> >
> > 1. Backup, restore of such a large database
> > 2. Recovery of a broken database (A lost replica)
> > 3. Fixing a standby that lags a lot
> > 4. Triggering a PITR with any backup tools
> > 5. Maintenance at times
> > 6. Finding equivalents of oracle items (which is common during any
> > oracle to postgres migration)
> >
> > I dont see any limits in database/ objects as specified in https://
> > www.postgresql.org/docs/current/limits.html <https://www.postgresql.org/
> > docs/current/limits.html>
> >
> > Thanks and Regards,
> > Kavya
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Karsten Hilbert 2026-10-08 17:33:07 Re: Challenges with huge postgresql deployments in 300+ TBs
Previous Message Adrian Klaver 2026-10-08 14:50:10 Re: Challenges with huge postgresql deployments in 300+ TBs