Thread: pg_wal filling up while running huge updates
Hi,
We are doing an oracle to postgres migration(5 TB+ data). We are encoding and decoding BLOB data after migration and for that we are running updates on tables having BLOB/CLOB data. When we execute this pg_wal is filling up.
Do you have any general guidelines for migrating a 5TB + database from Oracle to Postgres? Any specific guidelines around archiving logs?
Regards,
Aditya.
On Fri, Aug 5, 2022 at 7:30 AM aditya desai <admad123@gmail.com> wrote:
We are doing an oracle to postgres migration(5 TB+ data). We are encoding and decoding BLOB data after migration and for that we are running updates on tables having BLOB/CLOB data. When we execute this pg_wal is filling up.Do you have any general guidelines for migrating a 5TB + database from Oracle to Postgres? Any specific guidelines around archiving logs?
If you use pgBackrest for WAL archiving, you could enable asynchronous archiving.
Don Seiler
www.seiler.us
www.seiler.us
On Fri, Aug 05, 2022 at 06:00:02PM +0530, aditya desai wrote: > Hi, > We are doing an oracle to postgres migration(5 TB+ data). We are encoding > and decoding BLOB data after migration and for that we are running updates > on tables having BLOB/CLOB data. When we execute this pg_wal is filling up. Could you please include basic information in each new thread you create ? https://wiki.postgresql.org/wiki/Server_Configuration https://wiki.postgresql.org/wiki/Guide_to_reporting_problems -- Justin