| From: | Saul Perdomo <saul(dot)perdomo(at)gmail(dot)com> |
|---|---|
| To: | Rama Krishnan <raghuldrag(at)gmail(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query about pg_wal directory filled up |
| Date: | 2024-12-19 00:00:14 |
| Message-ID: | CAN3jBgFTeXD2c+nejM9zvi1tG=CNuChqdU0C8cegc0j3B453MQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Dec 18, 2024, 5:01 a.m. Rama Krishnan <raghuldrag(at)gmail(dot)com> wrote:
>
> Hi Team,
>
> One of our clients recently migrated from Oracle to PostgreSQL and is
> conducting multiple scenarios to understand PostgreSQL behavior.
>
> One of their main concerns is whether the database will allow `INSERT`
> queries when the `pg_wal` directory becomes full.
>
>
The way out of this "conundrum" is to make sure to implement a solid backup
process.
I'm a huge fan of PGBackRest:
> Kindly advise
>
>
> Thanks
> RK
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Saul Perdomo | 2024-12-19 00:02:30 | Re: How to deal with dangling files after aborted `pg_restore`? |
| Previous Message | Adrian Klaver | 2024-12-18 23:11:36 | Re: Intermittent errors when fetching cursor rows on PostgreSQL 16 |