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 1swKyX-003DQz-TE for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Oct 2024 12:30:34 +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 1swKyV-00EhdV-Q9 for pgsql-bugs@arkaria.postgresql.org; Thu, 03 Oct 2024 12:30:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1swKyV-00EhdN-56 for pgsql-bugs@lists.postgresql.org; Thu, 03 Oct 2024 12:30:31 +0000 Received: from relay5-d.mail.gandi.net ([2001:4b98:dc4:8::225]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1swKyN-002LZm-6C for pgsql-bugs@lists.postgresql.org; Thu, 03 Oct 2024 12:30:30 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id B463A1C000B; Thu, 3 Oct 2024 12:30:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1727958621; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7Y4iIS2Joz/Olaa9CYFgA61pQng7be315jtdm0HOOrk=; b=YbYxDU9kcJDn8g6IGrqYrrLX2T28nrFI8qOmnr4hG/XNVfU96BiUVKPTtqiaSDXmelIJqy FUDpd0oJjsM9XAmXOjq9dcBWiYX01XeaY8Yh53IJ4RSXz50xk060NLzr5ogs39pxg+WHWS cwpO3Xp4G5YEv4rFvhxyn27kuOI+zx/zkKC9sMGDV/SsVCpBe8bJYB9SF7cVF3mIQ2Im2s Ao4apB7Lv9r+D3QcmrPn695tVAon2c66Gc1DnMtg6XEHAgbyyanuE7Vnc06xHiJMf1bHdg yxlCfLM2tkBCJiczq0x1Az8+L1rPiepqkusXYGZelP//v3LWuny0bJgJAv9YHQ== Message-ID: Date: Thu, 3 Oct 2024 14:30:19 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18624: Memory Leak Issue with PostgreSQL Connection During COPY Command Execution. To: Abhishek Mittal , Tom Lane Cc: Junwang Zhao , pgsql-bugs@lists.postgresql.org References: <18624-451f53141608af60@postgresql.org> <2466048.1726854902@sss.pgh.pa.us> Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/3/24 11:49, Abhishek Mittal wrote: > Hi, > > I'm currently facing a blocker in my project. Could we please check this > issue. > > Thank you for your assistance. > Please, don't top post. Reply in-line. You have not reported if you tried upgrading to 12.20. Chances are this issue was already fixed since 12.16, people are unlikely to spend time investigating this, only to find it was a waste of time. Also, Tom asked you a couple important questions you ignored: > If updating to 12.20 does not resolve the problem, then we are > going to need more information. Is this straight community > Postgres, or some variant? If you built it yourself, what > options did you use? Do you have any extensions installed? Please provide this info. It was suggested to try with "jit=off", so maybe try that too - I personally don't see why would that matter for the COPY command, but maybe it does ... Finally, I wonder if you're simply misinterpreting what RES means. It's not "private memory used by the process". So if you're simply seeing RES to grow to 10GB and conclude "memory leak", it may not be the case. It could be shared memory, for example - you need to inspect "smaps" for the process to see what exactly the RES figure includes. regards -- Tomas Vondra