Request a Demo
Home   >   mailing lists

Re: Challenges with huge postgresql deployments in 300+ TBs - Mailing list pgsql-general

From Juan Rodrigo Alejandro Burgos Mella
Subject Re: Challenges with huge postgresql deployments in 300+ TBs
Date
Msg-id CAHbZ42y7hB2NSyd7+42sftChb9nNshNt19M9kTabR8504QjxxQ@mail.gmail.com
Whole thread
In response to Challenges with huge postgresql deployments in 300+ TBs  (kavya chandren <kavyachandren@gmail.com>)
List pgsql-general
Tree view
Some things that came up in a migration that i participated:
- Refactoring from PL/SQL to PL/pgSQL
- If there is SP (functions, procedures, triggers) DML must be brought to ANSI SQL
- Validate field data types, anticipating transformation edges
- Atomicity and Rollback, in PostgreSQL transactions are canceled for complete when there is an error.
- PostgreSQL does not support autonomous transactions (PRAGMA AUTONOMOUS_TRANSACTION)
- PostgreSQL does not contemplate Synonyms.

I hope it helps you

Atte
JRBM

El jue, 8 oct 2026 a las 3:16, kavya chandren (<kavyachandren@gmail.com>) escribió:
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.

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

Thanks and Regards,
Kavya  

pgsql-general by date:

Previous
From: Manu
Date:
Subject: Re: Challenges with huge postgresql deployments in 300+ TBs
Next
From: Alban Hertroys
Date:
Subject: Re: Challenges with huge postgresql deployments in 300+ TBs