From: Adrian Klaver <adrian.klaver@aklaver.com>
To: kavya chandren <kavyachandren@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Challenges with huge postgresql deployments in 300+ TBs
Date: Thu, 8 Oct 2026 12:41:37 -0700
Message-ID: <dc1f76cd-3a3a-4866-b858-c7251fed3d6a@aklaver.com> (raw)
In-Reply-To: <CAPXWBGY8OBgFrTUfMAqWgiYVK-Hc1CvUaREhPGwGYwHvK2sGXg@mail.gmail.com>
References: <CAPXWBGai9XJdoikZXt_7-XmUHF5iSTkKpM3cQnk2xVQVcou8dQ@mail.gmail.com>
<96a0c9d6-d9ef-491e-8783-36b2f4840fe3@aklaver.com>
<CAPXWBGY8OBgFrTUfMAqWgiYVK-Hc1CvUaREhPGwGYwHvK2sGXg@mail.gmail.com>
On 10/8/26 8:56 AM, kavya chandren wrote:
> Hi Adrian,
>
> Intention is to get away from Oracle and get committed to Open source
> Postgresql.
Alright I understand.
Not sure what your timeline and resources are, but I would start with a
test setup using a subset of the existing Oracle setup and work against
that to do an initial determination of the challenges.
>
> On Thu, Oct 8, 2026 at 8:20 PM Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.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 <http://
> www.postgresql.org/docs/current/limits.html> <https://
> www.postgresql.org/ <https://www.postgresql.org/;
> > docs/current/limits.html>
> >
> > Thanks and Regards,
> > Kavya
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: adrian.klaver@aklaver.com, kavyachandren@gmail.com
Subject: Re: Challenges with huge postgresql deployments in 300+ TBs
In-Reply-To: <dc1f76cd-3a3a-4866-b858-c7251fed3d6a@aklaver.com>
References: <CAPXWBGai9XJdoikZXt_7-XmUHF5iSTkKpM3cQnk2xVQVcou8dQ@mail.gmail.com> <96a0c9d6-d9ef-491e-8783-36b2f4840fe3@aklaver.com> <CAPXWBGY8OBgFrTUfMAqWgiYVK-Hc1CvUaREhPGwGYwHvK2sGXg@mail.gmail.com> <dc1f76cd-3a3a-4866-b858-c7251fed3d6a@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox