MIME-Version: 1.0
References: <CAJWX+EMoXWiSu3Jev9p71VmZ+jGBKuYg3J2r5ZDxsuuKpPbHcw@mail.gmail.com>
In-Reply-To: <CAJWX+EMoXWiSu3Jev9p71VmZ+jGBKuYg3J2r5ZDxsuuKpPbHcw@mail.gmail.com>
From: Saul Perdomo <saul.perdomo@gmail.com>
Date: Wed, 18 Dec 2024 19:00:14 -0500
Message-ID: <CAN3jBgFTeXD2c+nejM9zvi1tG=CNuChqdU0C8cegc0j3B453MQ@mail.gmail.com>
Subject: Re: Query about pg_wal directory filled up
To: Rama Krishnan <raghuldrag@gmail.com>
Cc: Postgres General <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000d0aa2f06299437da"
Archived-At: <https://www.postgresql.org/message-id/CAN3jBgFTeXD2c%2BnejM9zvi1tG%3DCNuChqdU0C8cegc0j3B453MQ%40mail.gmail.com>
Precedence: bulk

--000000000000d0aa2f06299437da
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Dec 18, 2024, 5:01=E2=80=AFa.m. Rama Krishnan <raghuldrag@gmail.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:

https://pgbackrest.org/


> Kindly advise
>
>
> Thanks
> RK
>

--000000000000d0aa2f06299437da
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote gmail_quote_contai=
ner"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Dec 18, 2024, 5:01=E2=80=
=AFa.m. Rama Krishnan &lt;<a href=3D"mailto:raghuldrag@gmail.com">raghuldra=
g@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div><br clear=3D"all"></div><div><div dir=3D"ltr" class=3D"gmail_=
signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><span style=
=3D"font-family:comic sans ms,sans-serif">Hi Team,</span><div></div></div><=
div dir=3D"ltr"><br></div><div>One of our clients recently migrated from Or=
acle to PostgreSQL and is conducting multiple scenarios to understand Postg=
reSQL behavior. =C2=A0<br><br>One of their main concerns is whether the dat=
abase will allow `INSERT` queries when the `pg_wal` directory becomes full.=
 =C2=A0<br><br></div></div></div></div></blockquote></div></div><div dir=3D=
"auto"><br></div><div dir=3D"auto">The way out of this &quot;conundrum&quot=
; is to make sure to implement a solid backup process.=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I&#39;m a huge fan of PGBackRest:</di=
v><div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://pgbackre=
st.org/">https://pgbackrest.org/</a></div><div dir=3D"auto"><br></div><div =
dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_quote gmail_qu=
ote_container"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div di=
r=3D"ltr" class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div=
><br>Kindly advise<br></div><div><br></div><div><br></div><div>Thanks</div>=
<div>RK</div></div></div></div>
</blockquote></div></div></div>

--000000000000d0aa2f06299437da--