| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | aditya desai <admad123(at)gmail(dot)com> |
| Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_wal filling up while running huge updates |
| Date: | 2022-08-05 13:56:52 |
| Message-ID: | CAHJZqBBMZfL9Z9Dig9HkQ1OQYxtNcobyA+T_KH1zWhSwiQeGqg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Aug 5, 2022 at 7:30 AM aditya desai <admad123(at)gmail(dot)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.
https://pgbackrest.org/configuration.html#section-archive/option-archive-async
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-08-05 14:04:00 | Re: pg_wal filling up while running huge updates |
| Previous Message | aditya desai | 2022-08-05 12:30:02 | pg_wal filling up while running huge updates |