From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jean-Christophe Boggio <postgresql@thefreecat.org>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Date: Fri, 13 Oct 2023 11:02:04 -0400
Message-ID: <1528962.1697209324@sss.pgh.pa.us> (raw)
In-Reply-To: <b9a4bf45-65ca-4598-beae-84e269331fbb@thefreecat.org>
References: <1018f9c0-9d14-4146-b7e9-24c48ea29e1d@thefreecat.org>
<897a43b3-60d0-2417-f821-9299fd204c1d@sqlexec.com>
<b9a4bf45-65ca-4598-beae-84e269331fbb@thefreecat.org>
Jean-Christophe Boggio <postgresql@thefreecat.org> writes:
> You can find the corresponding logs attached.
Your query seems to be creating TupleSort contexts and then leaking
them, which is surely a bug. Can you make a self-contained test
case that reproduces this?
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, postgresql@thefreecat.org, pgsql-admin@lists.postgresql.org
Subject: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
In-Reply-To: <1528962.1697209324@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