From: Tom Lane <tgl@sss.pgh.pa.us>
To: higherone@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17602: Query backend process killed because it uses up all memory.
Date: Tue, 30 Aug 2022 15:01:31 -0400
Message-ID: <3727393.1661886091@sss.pgh.pa.us> (raw)
In-Reply-To: <17602-b072900fa964cabf@postgresql.org>
References: <17602-b072900fa964cabf@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> I'm writing to seek for generic help on trouble shooting bugs related to
> query backend process killed because of memory exhaust on this single query
> process.
Try starting the server under a restrictive ulimit, so that it will
get ENOMEM failure before it bloats to the point of receiving an
OOM kill. Aside from being more friendly to other server processes,
this should result in getting a memory consumption map dumped to
postmaster stderr when the failure is hit. Seeing which context
is getting bloated would be pretty useful information.
On Linux I believe "ulimit -v" is the most appropriate setting to
change.
regards, tom lane
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: tgl@sss.pgh.pa.us, higherone@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17602: Query backend process killed because it uses up all memory.
In-Reply-To: <3727393.1661886091@sss.pgh.pa.us>
* 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