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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jean-Christophe Boggio <postgresql(at)thefreecat(dot)org>
Cc: pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: One PG process eating more than 40GB of RAM and getting killed by OOM
Date: 2023-10-13 19:38:43
Message-ID: 1564639.1697225923@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Jean-Christophe Boggio <postgresql(at)thefreecat(dot)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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message M Sarwar 2023-10-13 21:53:16 Connecting 2 databases within the same instance
Previous Message Jean-Christophe Boggio 2023-10-13 19:12:02 Re: One PG process eating more than 40GB of RAM and getting killed by OOM