| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | kavya chandren <kavyachandren(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Challenges with huge postgresql deployments in 300+ TBs |
| Date: | 2026-10-08 14:50:10 |
| Message-ID: | 96a0c9d6-d9ef-491e-8783-36b2f4840fe3@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | kavya chandren | 2026-10-08 15:56:19 | Re: Challenges with huge postgresql deployments in 300+ TBs |
| Previous Message | Ray O'Donnell | 2026-10-08 14:48:03 | Re: Challenges with huge postgresql deployments in 300+ TBs |