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 1rg2JP-003opr-4L for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Mar 2024 12:48:28 +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 1rg2JN-00DJ2p-01 for pgsql-bugs@arkaria.postgresql.org; Fri, 01 Mar 2024 12:48:25 +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 1rg2JM-00DJ2h-JH for pgsql-bugs@lists.postgresql.org; Fri, 01 Mar 2024 12:48:25 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rg2JI-002KDE-FS for pgsql-bugs@lists.postgresql.org; Fri, 01 Mar 2024 12:48:23 +0000 Received: from [172.30.8.38] (unknown [172.30.8.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: a.lepikhov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 1A7B8E210DF; Fri, 1 Mar 2024 15:48:16 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1709297298; bh=q6UerClmVJt7tUEPdTRheRkThPe6Xc2UnMwE+tjkfBo=; h=Message-ID:Date:User-Agent:Subject:To:References:From:In-Reply-To: From; b=WoYdwnXKsMym2zOfl6GQBAJjvP8O+B4D55LgkjBy8PdU/Nq2K/ISVZLCkS0zeCGxr QbWnVAq3Ml/YOsDuj4gxyhAnQQyvxbQuBFgw/kv4UGWCpJEJEM0Fzg1KjLce6cUnAF tNXkRv41i0xHcCYMH0r7dzPhU44OrBTi9dkcZtN2PzjTNsKrr0UVStLAgug0aZYaLh pm2myTfa8esL19xcorqPUHDXrouS9jOgngCWYOdmJpLZqtZQRqj+iWxr2Og8h8/J6F DQIPbhuwg+UkoYNNAVjItePHbF8FC6zOM7vCmqQI2pPKcmhpkKsdVjmopKJ40FI//1 nlQwkvQtSnz9Q== Message-ID: <90092199-55cd-4fa3-a608-9a41d8e76c44@postgrespro.ru> Date: Fri, 1 Mar 2024 19:48:14 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: BUG #18349: ERROR: invalid DSA memory alloc request size 1811939328, CONTEXT: parallel worker Content-Language: en-US To: Alexey Ermakov , Tomas Vondra , pgsql-bugs@lists.postgresql.org References: <18349-83d33dd3d0c855c3@postgresql.org> <512ef568-336e-4087-ba23-f22b006d329d@postgrespro.ru> <7a1f5e5b-632f-4cc5-8078-b18a848e8924@postgrespro.ru> <2ff6260b-8722-b301-cf7e-4e66a159778c@dataegret.com> From: Andrei Lepikhov Organization: Postgres Professional In-Reply-To: <2ff6260b-8722-b301-cf7e-4e66a159778c@dataegret.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/3/2024 16:50, Alexey Ermakov wrote: > Hello! I reproduced generation of multiple temporary files and abnormal > memory > usage (in 'top' output both backend and parallel worker used around > 3-4GB of > RAM each, I often got OOM killer) but not memory allocation error so far. Could you provide a backtrace at the moment of the error? It can show us exact place of the error without guesses. -- regards, Andrei Lepikhov Postgres Professional