Re: One PG process eating more than 40GB of RAM and getting killed by OOM - Mailing list pgsql-admin

From Tom Lane
Subject Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Date
Msg-id 1564639.1697225923@sss.pgh.pa.us
Whole thread Raw
In response to Re: One PG process eating more than 40GB of RAM and getting killed by OOM  (Jean-Christophe Boggio <postgresql@thefreecat.org>)
List pgsql-admin
Jean-Christophe Boggio <postgresql@thefreecat.org> writes:
> Le 13/10/2023 à 18:48, Jeff Janes a écrit :
>> We can see what the problem is (over 137,000 concurrent tuple sorts), 
>> but we can't tell what is ultimately causing it.  You will need to dig 
>> into, or disclose, the contents of the procedure.

> I have no problem disclosing this code and data to the PG dev team (this 
> is client data though so please keep it for yourselves). Where can I 
> send you a link to the dump ?

I'm interested in taking a look, you can send me the link privately.

            regards, tom lane



pgsql-admin by date:

Previous
From: Jean-Christophe Boggio
Date:
Subject: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Next
From: M Sarwar
Date:
Subject: Connecting 2 databases within the same instance