Message-ID: <ea673880dd25ed8dc6c594874186d196502c1644.camel@cybertec.at>
Subject: Re: Query about pg_wal directory filled up
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Rama Krishnan <raghuldrag@gmail.com>, Postgres General
	 <pgsql-general@postgresql.org>
Date: Wed, 18 Dec 2024 15:28:43 +0100
In-Reply-To: <CAJWX+EMoXWiSu3Jev9p71VmZ+jGBKuYg3J2r5ZDxsuuKpPbHcw@mail.gmail.com>
References: 
	<CAJWX+EMoXWiSu3Jev9p71VmZ+jGBKuYg3J2r5ZDxsuuKpPbHcw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.2 (3.54.2-1.fc41) 
MIME-Version: 1.0
Archived-At: <https://www.postgresql.org/message-id/ea673880dd25ed8dc6c594874186d196502c1644.camel%40cybertec.at>
Precedence: bulk

On Tue, 2024-12-17 at 19:11 +0530, Rama Krishnan wrote:
> One of their main concerns is whether the database will allow `INSERT` qu=
eries
> when the `pg_wal` directory becomes full. =C2=A0
>=20
> As I understand, once the `pg_wal` directory is completely filled, the da=
tabase
> will allow only read queries and will not permit any write operations. =
=C2=A0

That is not the case.  If pg_wal fills up (more precisely: if creating a ne=
w
file in pg_wal fails), PostgreSQL will crash and go down.

Yours,
Laurenz Albe