Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qrNzl-003zfL-47 for pgsql-admin@arkaria.postgresql.org; Fri, 13 Oct 2023 19:38:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qrNzi-0037mn-Sn for pgsql-admin@arkaria.postgresql.org; Fri, 13 Oct 2023 19:38:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qrNzi-0037mf-HY for pgsql-admin@lists.postgresql.org; Fri, 13 Oct 2023 19:38:47 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qrNzg-000Kxw-LC for pgsql-admin@lists.postgresql.org; Fri, 13 Oct 2023 19:38:46 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 39DJchu61564640; Fri, 13 Oct 2023 15:38:43 -0400 From: Tom Lane To: Jean-Christophe Boggio cc: pgsql-admin Subject: Re: One PG process eating more than 40GB of RAM and getting killed by OOM In-reply-to: <416d1607-4650-4624-b8e5-46f8a674aebf@thefreecat.org> References: <1018f9c0-9d14-4146-b7e9-24c48ea29e1d@thefreecat.org> <897a43b3-60d0-2417-f821-9299fd204c1d@sqlexec.com> <416d1607-4650-4624-b8e5-46f8a674aebf@thefreecat.org> Comments: In-reply-to Jean-Christophe Boggio message dated "Fri, 13 Oct 2023 21:12:02 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1564638.1697225923.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Fri, 13 Oct 2023 15:38:43 -0400 Message-ID: <1564639.1697225923@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Jean-Christophe Boggio 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