From: Laurenz Albe <laurenz.albe@cybertec.at>
To: sibowu@amazon.com
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19054: Memory exhaustion vulnerability in PostgreSQL array operations leads to server crash
Date: Mon, 15 Sep 2025 22:30:17 +0200
Message-ID: <0513e4694c2f7264f469fa5febc1662001f0a903.camel@cybertec.at> (raw)
In-Reply-To: <19054-b3e91211012e644a@postgresql.org>
References: <19054-b3e91211012e644a@postgresql.org>
On Mon, 2025-09-15 at 20:00 +0000, PG Bug reporting form wrote:
> PostgreSQL's array implementation can lead to server crashes due to
> uncontrolled memory consumption during array operations. When performing
> continuous array modifications within a loop, the server eventually exhausts
> available memory and crashes, affecting all connected sessions.
That's not a bug, that's a user error.
For reliable operation, you have to disable Linux' memory overcommit.
Then the kernel won't kill the database, but your query will receive an
"out of memory" error and fail without any crashes.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: laurenz.albe@cybertec.at, sibowu@amazon.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19054: Memory exhaustion vulnerability in PostgreSQL array operations leads to server crash
In-Reply-To: <0513e4694c2f7264f469fa5febc1662001f0a903.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox