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 1qgwWU-000Lyc-J6 for pgsql-bugs@arkaria.postgresql.org; Fri, 15 Sep 2023 00:17:26 +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 1qgwWR-00BiKJ-LW for pgsql-bugs@arkaria.postgresql.org; Fri, 15 Sep 2023 00:17:23 +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 1qgwWR-00BiJf-Bj for pgsql-bugs@lists.postgresql.org; Fri, 15 Sep 2023 00:17:23 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qgwWN-0058LO-Tw for pgsql-bugs@lists.postgresql.org; Fri, 15 Sep 2023 00:17:22 +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 38F0HGTC3207311; Thu, 14 Sep 2023 20:17:16 -0400 From: Tom Lane To: wobbet@wobbet.com, Robert Sanford cc: pgsql-bugs@lists.postgresql.org Subject: Re: Segmentation Fault In-reply-to: References: <3030992.1694649537@sss.pgh.pa.us> Comments: In-reply-to Robert Sanford message dated "Thu, 14 Sep 2023 14:29:20 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3207309.1694737036.1@sss.pgh.pa.us> Date: Thu, 14 Sep 2023 20:17:16 -0400 Message-ID: <3207310.1694737036@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Robert Sanford writes: > I'm trying to get a core dump but I can't seem to actually generate one. > ... > I then restarted the postgres server. When I look at the limits in the pid > folder I see... > Limit Soft Limit Hard Limit Units > Max cpu time unlimited unlimited seconds > Max file size unlimited unlimited bytes > Max data size unlimited unlimited bytes > Max stack size 8388608 unlimited bytes > Max core file size 0 unlimited bytes This shows that you are now allowed to set "ulimit -c unlimited", but you have not actually done so, at least not in the session that you're using to inspect these settings. If you are starting the server "by hand" (from a manual shell command), it should work to do "ulimit -c unlimited" before issuing the command to start the server. If you are using infrastructure such as systemd or initscripts, then you'll need to figure out how to get it to set the ulimit in the environment of the server process. BTW, have you tried disabling JIT to see if that stops the crashes? regards, tom lane