Re: One PG process eating more than 40GB of RAM and getting killed by OOM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jean-Christophe Boggio <postgresql@xxxxxxxxxxxxxx>
Subject: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
From: Tom Lane <tgl@xxxxxxxxxxxxx>
Date: Fri, 13 Oct 2023 11:02:04 -0400
Cc: pgsql-admin@xxxxxxxxxxxxxxxxxxxx
Comments: In-reply-to Jean-Christophe Boggio <postgresql@xxxxxxxxxxxxxx> message dated "Fri, 13 Oct 2023 16:31:21 +0200"
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@xxxxxxxxxxxxxx> 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

References:
- One PG process eating more than 40GB of RAM and getting killed by OOM
  - From: Jean-Christophe Boggio
- Re: One PG process eating more than 40GB of RAM and getting killed by OOM
  - From: MichaelDBA
- Re: One PG process eating more than 40GB of RAM and getting killed by OOM
  - From: Jean-Christophe Boggio

Prev by Date: Re: Locks analyze
Next by Date: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Previous by thread: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Next by thread: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Home] [Postgresql General] [Postgresql Performance] [Postgresql PHP] [Postgresql Jobs] [PHP Users] [PHP Databases] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Yosemite Forum]

Powered by Linux